Triple
T10580758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butch Trucks |
E249727
|
entity |
| Predicate | relationshipToRelative |
P94755
|
FINISHED |
| Object | uncle of Derek Trucks |
—
|
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: uncle of Derek Trucks | Statement: [Butch Trucks, relationshipToRelative, uncle of Derek Trucks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToRelative Context triple: [Butch Trucks, relationshipToRelative, uncle of Derek Trucks]
-
A.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
B.
relationshipToMother
Indicates the specific familial or social connection an entity has to its mother.
-
C.
relationshipToChildren
Indicates the type of familial or social connection an entity has to one or more children.
-
D.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
E.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
- F. None of above. chosen
Provenance (4 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52759faa4819081c195488803ada9 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:38 p.m.