Triple
T13255773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fallout 76 |
E315653
|
entity |
| Predicate | timelineStartYear |
P10338
|
FINISHED |
| Object | 2102 |
—
|
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: 2102 | Statement: [Fallout 76, timelineStartYear, 2102]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timelineStartYear Context triple: [Fallout 76, timelineStartYear, 2102]
-
A.
chronologyStart
Indicates the point in time at which a sequence, event, or temporal record begins.
-
B.
beganInYear
chosen
Indicates that an event, process, or state started in a specific calendar year.
-
C.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
-
D.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
E.
notableEraStart
Indicates the point in time when a notable or historically significant era associated with an entity begins.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:24 p.m.