Triple
T30046512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars: X-Wing vs. TIE Fighter |
E763468
|
entity |
| Predicate | universeFaction |
P167547
|
FINISHED |
| Object | Rebel Alliance |
—
|
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: Rebel Alliance | Statement: [Star Wars: X-Wing vs. TIE Fighter, universeFaction, Rebel Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeFaction Context triple: [Star Wars: X-Wing vs. TIE Fighter, universeFaction, Rebel Alliance]
-
A.
gameFaction
chosen
Indicates that an entity belongs to, is aligned with, or is a member of a particular faction within a game.
-
B.
galacticConflict
Indicates a hostile or adversarial interaction occurring between entities at a galactic scale, such as war, large-scale disputes, or armed confrontation across multiple star systems.
-
C.
baseOfOperationsGalaxy
Indicates that a galaxy serves as the primary base of operations or main area of activity for an entity.
-
D.
factionType
Indicates the classification or category of a faction within a broader system or context.
-
E.
eraInUniverse
Indicates the specific time period or era during which something exists or occurs within a particular fictional or defined universe.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 6:54 p.m.