Triple
T10864218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida–Georgia football game |
E256485
|
entity |
| Predicate | annualSeriesSince |
P6469
|
FINISHED |
| Object | 1926 |
—
|
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: 1926 | Statement: [Florida–Georgia football game, annualSeriesSince, 1926]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualSeriesSince Context triple: [Florida–Georgia football game, annualSeriesSince, 1926]
-
A.
annualFrom
chosen
Indicates that something recurs or is calculated on a yearly basis starting from a specified point in time.
-
B.
seasonSeriesPlayedPerYear
Indicates the number of series played in a season during a given year.
-
C.
isAnnual
Indicates that something occurs, is scheduled, or is valid once every year.
-
D.
activatedAnnuallyUntil
Indicates that an action or state is activated once each year and continues to do so repeatedly up to, but not beyond, a specified end date.
-
E.
seasonYears
Indicates the span of calendar years during which a particular season (e.g., of a show, competition, or activity) takes place or is valid.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7516b2f148190adbacd35fc8c2056 |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.