Triple
T27769475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACC Championship 2013 |
E701700
|
entity |
| Predicate | recordOfFloridaStateBeforeGame |
P177525
|
FINISHED |
| Object | 12–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: 12–0 | Statement: [ACC Championship 2013, recordOfFloridaStateBeforeGame, 12–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordOfFloridaStateBeforeGame Context triple: [ACC Championship 2013, recordOfFloridaStateBeforeGame, 12–0]
-
A.
rankingOfFloridaStateBeforeGame
Indicates the competitive ranking position assigned to Florida State prior to the start of a specific game.
-
B.
buccaneersRecordEnteringGame
Indicates the win-loss (and possibly tie) record the Buccaneers team held immediately before a specific game began.
-
C.
ohioStateRecordEnteringGame
Indicates the statistical record held by Ohio State University’s team immediately before a specific game begins.
-
D.
buccaneersReputationBeforeGame
Indicates the perceived reputation or standing of the Buccaneers prior to the start of a specific game.
-
E.
Indiana StateRecordEnteringGame
Indicates that a team or player is entering a game holding a state-level record in Indiana.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 27, 2026, 4:33 p.m.