Triple
T24102627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Hunt (engineer) |
E597122
|
entity |
| Predicate | James HuntRelationship |
P155068
|
FINISHED |
| Object | younger 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: younger brother | Statement: [David Hunt (engineer), James HuntRelationship, younger brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: James HuntRelationship Context triple: [David Hunt (engineer), James HuntRelationship, younger brother]
-
A.
relationshipToJamesBond
Indicates the specific familial, romantic, professional, or social relationship that one entity has to James Bond.
-
B.
notableFormerDriver
Indicates that a person was previously a prominent or distinguished driver for the referenced entity (such as a team, organization, or company).
-
C.
motorsportRole
Indicates the specific function or position an entity holds within the context of motorsport activities or events.
-
D.
numberOfF1WorldChampionships
Indicates the number of Formula 1 World Championship titles that an entity has won.
-
E.
numberOfTimesF1RunnerUp
Indicates the number of times an entity has finished as the runner-up in Formula 1.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd2ad01881909aa5a3c300009086 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 11 p.m.