Triple
T35154091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Younger family |
E1015069
|
entity |
| Predicate | hasChildMember |
P7638
|
FINISHED |
| Object | Travis Younger |
—
|
NE NERFINISHED |
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: Travis Younger | Statement: [Younger family, hasChildMember, Travis Younger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildMember Context triple: [Younger family, hasChildMember, Travis Younger]
-
A.
hasSiblingMembers
Indicates that two entities are members of a group or organization and are siblings to each other within that membership context.
-
B.
hasMembers
chosen
Indicates that a group, organization, or collection includes certain entities as its members.
-
C.
hasMembersWith
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
D.
hasSuccessorMembers
Indicates that one set of members follows or replaces another set of members in a sequence, order, or organizational structure.
-
E.
hasAssociateMember
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:02 p.m.