Triple
T9310677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasi (prince) of Israel |
E223997
|
entity |
| Predicate | heldByGroup |
P28720
|
FINISHED |
| Object | descendants of Hillel the Elder |
—
|
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: descendants of Hillel the Elder | Statement: [Nasi (prince) of Israel, heldByGroup, descendants of Hillel the Elder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByGroup Context triple: [Nasi (prince) of Israel, heldByGroup, descendants of Hillel the Elder]
-
A.
heldByMembersOf
chosen
Indicates that something is possessed, controlled, or owned collectively by the members of a specified group or organization.
-
B.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
C.
heldByInCapacityAs
Indicates that something is held or possessed by an entity specifically in a defined role, function, or official capacity rather than in a general or personal sense.
-
D.
usedByGroup
Indicates that something is utilized or employed by a particular group or collective entity.
-
E.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ac17488190aa6acf7a61420632 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.