Triple
T34368876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Thorndyke |
E882096
|
entity |
| Predicate | relationshipToJimDouglas |
P205410
|
FINISHED |
| Object | business rival |
—
|
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: business rival | Statement: [Peter Thorndyke, relationshipToJimDouglas, business rival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToJimDouglas Context triple: [Peter Thorndyke, relationshipToJimDouglas, business rival]
-
A.
relationshipToJimDear
Indicates a familial, romantic, or otherwise significant personal relationship that an entity has with the person referred to as Jim Dear.
-
B.
relationshipTypeWithEdwardDouglas
Indicates the specific nature or category of relationship that an entity has with Edward Douglas.
-
C.
relationshipToDouglasSpaulding
Indicates the specific type of personal or social relationship an entity has with Douglas Spaulding.
-
D.
relationshipToJoeGillis
Indicates the specific type of personal or social relationship that one entity has to Joe Gillis.
-
E.
relationshipToJoeBuck
Indicates the specific familial, social, or professional relationship that one entity has to the person Joe Buck.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:58 a.m.