Triple
T3538144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars sequel trilogy |
E74814
|
entity |
| Predicate | beganReleaseYear |
P7549
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Star Wars sequel trilogy, beganReleaseYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganReleaseYear Context triple: [Star Wars sequel trilogy, beganReleaseYear, 2015]
-
A.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
B.
productionStartYear
Indicates the year in which the production of an item, work, or entity first began.
-
C.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
-
D.
firstSeriesYear
Indicates the year in which a series (such as a TV show, book series, or sports league season) first began or was initially released.
-
E.
debutYear
chosen
Indicates the year in which an entity first appeared, was introduced, or made its initial public debut.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcc928248190b851f8280d58cfcf |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.