Triple
T1805688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars |
E40213
|
entity |
| Predicate | hasCanon |
P977
|
FINISHED |
| Object | Star Wars canon (post-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: Star Wars canon (post-2014) | Statement: [Star Wars, hasCanon, Star Wars canon (post-2014)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanon Context triple: [Star Wars, hasCanon, Star Wars canon (post-2014)]
-
A.
hasClosedCanon
Indicates that a body of authoritative texts is considered complete and no additional works can be added to it.
-
B.
usesCanon
Indicates that one entity employs or relies on another entity as its standard, reference, or authoritative source.
-
C.
inCanonOf
chosen
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with another entity.
-
D.
usesCanons
Indicates that one entity employs or makes use of canons (such as rules, principles, or artillery pieces) in relation to another entity or context.
-
E.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d514c081908197ac1f7c7d7a88 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.