Triple
T856625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Landry |
E18506
|
entity |
| Predicate | consecutiveWinningSeasons |
P20669
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Tom Landry, consecutiveWinningSeasons, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecutiveWinningSeasons Context triple: [Tom Landry, consecutiveWinningSeasons, 20]
-
A.
consecutiveWinsInSeason
Indicates that one entity achieved a specified number of back-to-back victories within a single season.
-
B.
mostConsecutiveWinsCount
Indicates the highest number of wins achieved in a row within a given sequence or context.
-
C.
regularSeasonWins
Indicates the number of games a team wins during the regular season of a competition.
-
D.
consecutiveGamesPlayed
Indicates that an entity has participated in a series of games without interruption, one immediately following another.
-
E.
seasonRecordWins
Indicates the number of games a team has won during a specific season.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac4d47508190b48d944aa2d881bf |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4893e481908632102d240466dc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.