Triple
T13802333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civilization franchise |
E331669
|
entity |
| Predicate | timeSpanCoveredInGame |
P110188
|
FINISHED |
| Object | ancient era to near future |
—
|
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: ancient era to near future | Statement: [Civilization franchise, timeSpanCoveredInGame, ancient era to near future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanCoveredInGame Context triple: [Civilization franchise, timeSpanCoveredInGame, ancient era to near future]
-
A.
timeHorizonCovered
chosen
Indicates the span or duration of time that is encompassed or addressed by something (such as a plan, forecast, or agreement).
-
B.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
C.
startTimeRelativeToGame
Indicates the time at which an event or action occurs, expressed relative to the start time of the game rather than as an absolute timestamp.
-
D.
gameLength
Indicates the duration or total length of a game, typically measured in time or turns.
-
E.
monthPlayed
Indicates the month during which an activity, event, or game was played or took place.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ded6c8190851c108ae559a355 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.