Triple
T37620265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 BCS National Championship |
E936047
|
entity |
| Predicate | FloridaStateRecordBeforeGame |
P177525
|
FINISHED |
| Object | 13–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: 13–0 | Statement: [2013 BCS National Championship, FloridaStateRecordBeforeGame, 13–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FloridaStateRecordBeforeGame Context triple: [2013 BCS National Championship, FloridaStateRecordBeforeGame, 13–0]
-
A.
recordOfFloridaStateBeforeGame
chosen
Indicates the win–loss record held by Florida State prior to the referenced game.
-
B.
rankingOfFloridaStateBeforeGame
Indicates the competitive ranking position assigned to Florida State prior to the start of a specific game.
-
C.
recordOfDukeBeforeGame
Indicates the performance record or statistics associated with Duke prior to a specific game.
-
D.
buccaneersRecordEnteringGame
Indicates the win-loss (and possibly tie) record the Buccaneers team held immediately before a specific game began.
-
E.
buccaneersReputationBeforeGame
Indicates the perceived reputation or standing of the Buccaneers prior to the start of a specific game.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.