Triple
T31283038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crix Madine |
E797725
|
entity |
| Predicate | canonLegendsStatus |
P168783
|
FINISHED |
| Object | Star Wars Legends |
—
|
NE NERFINISHED |
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: Star Wars Legends | Statement: [Crix Madine, canonLegendsStatus, Star Wars Legends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonLegendsStatus Context triple: [Crix Madine, canonLegendsStatus, Star Wars Legends]
-
A.
inCanonStatus
Indicates that an entity’s status is whether it is considered part of the official canon within a given fictional or narrative universe.
-
B.
franchiseCanonStatus
chosen
Indicates whether a work, event, or element is officially recognized as part of the established canon within a franchise.
-
C.
inCanonWith
Indicates that two or more works, events, or elements are officially recognized as belonging to the same narrative continuity or canon.
-
D.
storyCanonStatus
Indicates the canonical status of a story relative to an official or primary continuity.
-
E.
givesCanon
Indicates that one entity provides or establishes an official or authoritative version (canon) of something for another entity or context.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.