Triple
T29499641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TIE fighter |
E748330
|
entity |
| Predicate | manufacturerInCanon |
P166974
|
FINISHED |
| Object | Sienar Fleet Systems |
—
|
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: Sienar Fleet Systems | Statement: [TIE fighter, manufacturerInCanon, Sienar Fleet Systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manufacturerInCanon Context triple: [TIE fighter, manufacturerInCanon, Sienar Fleet Systems]
-
A.
canonCollectionKnownAs
Indicates that a canon collection is known or referred to by a particular name or title.
-
B.
usesCanon
Indicates that one entity employs or relies on another entity as its standard, reference, or authoritative source.
-
C.
givesCanon
Indicates that one entity provides or establishes an official or authoritative version (canon) of something for another entity or context.
-
D.
inCanonWith
Indicates that two or more works, events, or elements are officially recognized as belonging to the same narrative continuity or canon.
-
E.
inCanonStatus
Indicates that an entity’s status is whether it is considered part of the official canon within a given fictional or narrative universe.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c31f41c8190a8879069b4ec48af |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6642e676c8190af0e6b1416eed6d2 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 4:22 p.m.