Triple
T4230988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota Vikings–Detroit Lions rivalry |
E94579
|
entity |
| Predicate | eraOfVikingsDominance |
P5898
|
FINISHED |
| Object | late 1960s |
—
|
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: late 1960s | Statement: [Minnesota Vikings–Detroit Lions rivalry, eraOfVikingsDominance, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfVikingsDominance Context triple: [Minnesota Vikings–Detroit Lions rivalry, eraOfVikingsDominance, late 1960s]
-
A.
historicalEraOfRise
Indicates the historical era or period during which an entity first rose to prominence, influence, or significance.
-
B.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
C.
timePeriodOfDominance
chosen
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
D.
eraOfHistoricalKingdom
Indicates the historical time period during which a particular kingdom existed or held prominence.
-
E.
conquestPeriod
Indicates the time span during which one entity successfully subjugates or takes control of another through conquest.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e62e3c881909ffb9269ba9018b9 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.