Triple
T3592470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Shula |
E76056
|
entity |
| Predicate | perfectSeasonRecord |
P35351
|
FINISHED |
| Object | 17-0 |
—
|
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: 17-0 | Statement: [Don Shula, perfectSeasonRecord, 17-0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perfectSeasonRecord Context triple: [Don Shula, perfectSeasonRecord, 17-0]
-
A.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
-
B.
bestRegularSeasonRecord
Indicates that an entity (typically a team) achieved the highest overall performance record during the regular season compared to all others in the same competition.
-
C.
seasonRecord
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
D.
winsInSingleSeason
chosen
Indicates that one entity achieves a specified number of wins within a single competitive season.
-
E.
runnerUpRegularSeasonRecord
Indicates the regular season performance record (such as wins and losses) of the team that finished as runner-up.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15a546481909c72dac80d65e1fb |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.