Triple
T18676898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tackle |
E456622
|
entity |
| Predicate | isFinalPlayOfGame |
P21957
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Tackle, isFinalPlayOfGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFinalPlayOfGame Context triple: [The Tackle, isFinalPlayOfGame, true]
-
A.
hasFinishingMove
Indicates that one entity possesses or is associated with a specific, often decisive or signature, final action or move used to conclude an encounter or event.
-
B.
hasFinalMatch
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
C.
finalGameNumber
Indicates the specific number assigned to the last or concluding game in a series, season, or sequence of games.
-
D.
isFinalEngagementOf
chosen
Indicates that a given engagement is the last or concluding engagement in a sequence or series of engagements involving the same entities.
-
E.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
- F. None of above.
Provenance (3 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b66680819082a268f1bf857db5 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.