Triple
T32180771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooster Bennett |
E821973
|
entity |
| Predicate | relationshipToColtBennett |
P206216
|
FINISHED |
| Object | older brother |
—
|
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: older brother | Statement: [Rooster Bennett, relationshipToColtBennett, older brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToColtBennett Context triple: [Rooster Bennett, relationshipToColtBennett, older brother]
-
A.
relationshipWithJohnBennett
Indicates that there exists some specified type of relationship or association between an entity and John Bennett.
-
B.
relationshipToJoeBuck
Indicates the specific familial, social, or professional relationship that one entity has to the person Joe Buck.
-
C.
relationshipTypeWithRobertCohn
Indicates the specific nature or category of relationship that an entity has with Robert Cohn.
-
D.
relationshipToBenny
Indicates the specific type of personal or social relationship that an entity has with Benny.
-
E.
relationshipToRyanBingham
Indicates the specific type of personal or social relationship an entity has with Ryan Bingham.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:34 a.m.