Triple
T13662481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarei HaMeah |
E327032
|
entity |
| Predicate | profiles |
P91407
|
FINISHED |
| Object | prominent rabbinic figures |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: prominent rabbinic figures | Statement: [Sarei HaMeah, profiles, prominent rabbinic figures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: profiles Context triple: [Sarei HaMeah, profiles, prominent rabbinic figures]
-
A.
profileDirectory
Indicates the directory path where a user's or application's profile data is stored or managed.
-
B.
participantProfile
chosen
Indicates that an entity serves as the profile or descriptive record associated with a particular participant in an event, activity, or process.
-
C.
publicProfile
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
D.
portraitOn
Indicates that one entity is depicted as a portrait on the surface or medium of another entity.
-
E.
academicProfile
Indicates the relationship that captures an entity’s academic background, qualifications, and scholarly activities or achievements.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc620df208190afaccf3ddd10aa60 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.