Triple
T8497676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars Legends |
E201138
|
entity |
| Predicate | continuityResetYear |
P83053
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Star Wars Legends, continuityResetYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuityResetYear Context triple: [Star Wars Legends, continuityResetYear, 2014]
-
A.
cancellationYear
Indicates the year in which something (such as an event, contract, or service) was officially canceled or terminated.
-
B.
startServiceYear
Indicates the year in which an entity began providing a particular service or started its service-related activity.
-
C.
chronologyPreviousYear
Indicates that one time-related entity occurs exactly one calendar year before another in a chronological sequence.
-
D.
hasDiscontinuationApproxYear
Indicates that an entity ceased to exist, operate, or be available around a specified (approximate) calendar year.
-
E.
redefinitionYear
Indicates the year in which something was redefined, such as when its definition, scope, or formal status was officially changed.
- F. None of above. chosen
Provenance (4 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe583aebc819090345684bfa1fca2 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.