Triple
T8497675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars Legends |
E201138
|
entity |
| Predicate | continuityResetBy |
P11251
|
FINISHED |
| Object | Disney acquisition of Lucasfilm |
—
|
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: Disney acquisition of Lucasfilm | Statement: [Star Wars Legends, continuityResetBy, Disney acquisition of Lucasfilm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuityResetBy Context triple: [Star Wars Legends, continuityResetBy, Disney acquisition of Lucasfilm]
-
A.
continuityType
Indicates the specific manner or pattern in which continuity is maintained or transitions occur between related elements or states.
-
B.
continuityFrom
Indicates that one entity continues, extends, or proceeds directly from another in a seamless or unbroken manner.
-
C.
disruptsContinuityOf
Indicates that one entity interrupts, breaks, or otherwise prevents the ongoing, uninterrupted progression or sequence of another entity or process.
-
D.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
E.
scopeOfReset
chosen
Indicates the range or extent within which a reset action applies or takes effect.
- 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_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. |
Created at: March 30, 2026, 6:13 p.m.