Triple
T27769470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACC Championship 2013 |
E701700
|
entity |
| Predicate | quarterByQuarterScore_FloridaState |
P30630
|
FINISHED |
| Object | 0–17–21–7 |
—
|
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: 0–17–21–7 | Statement: [ACC Championship 2013, quarterByQuarterScore_FloridaState, 0–17–21–7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quarterByQuarterScore_FloridaState Context triple: [ACC Championship 2013, quarterByQuarterScore_FloridaState, 0–17–21–7]
-
A.
quarterScores
chosen
Indicates the scores achieved in each quarter of a game, match, or period-based event.
-
B.
finalFourCountFlorida
Indicates the number of times a Florida team has reached the Final Four in a given competition or context.
-
C.
scoringSummaryFourthQuarter
Indicates the scoring events or point totals that occurred during the fourth quarter of a game.
-
D.
quarterFinalAggregateScore
Indicates the combined total score for an entity across all legs or matches in a quarter-final round of a competition.
-
E.
scoringSummaryThirdQuarter
Indicates the summary of scoring events that occurred during the third quarter of a 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6379527cc8190b835dcf330096a64 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:33 p.m.