Triple
T7424522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Fox |
E171334
|
entity |
| Predicate | hasGivenNumber |
P76896
|
FINISHED |
| Object | NFL head coaching record over 100 regular-season wins |
—
|
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: NFL head coaching record over 100 regular-season wins | Statement: [John Fox, hasGivenNumber, NFL head coaching record over 100 regular-season wins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenNumber Context triple: [John Fox, hasGivenNumber, NFL head coaching record over 100 regular-season wins]
-
A.
hasGiven
Indicates that one entity has transferred or presented something to another entity.
-
B.
hasCallInNumber
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
-
C.
hasNumberInYear
Indicates that a specific number is associated with or occurs within a given year.
-
D.
containsNumber
Indicates that one entity includes or has at least one numeric value or digit within it.
-
E.
imoNumber
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f302b33481908eae877970f2bbdf |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1ee5ab8819091082324f2dc3b8c |
completed | March 27, 2026, 9:09 p.m. |
Created at: March 27, 2026, 3:12 p.m.