Triple
T29187888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Vonreg |
E739918
|
entity |
| Predicate | starfighterType |
P80077
|
FINISHED |
| Object | TIE fighter variant |
—
|
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: TIE fighter variant | Statement: [Major Vonreg, starfighterType, TIE fighter variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starfighterType Context triple: [Major Vonreg, starfighterType, TIE fighter variant]
-
A.
usesStarfighter
Indicates that one entity operates or employs a starfighter as its vehicle, tool, or means of transportation or combat.
-
B.
notableStarfighter
Indicates that an entity is a starfighter recognized for particular significance, prominence, or distinction (e.g., historically, tactically, or culturally).
-
C.
hasStarshipClassDepicted
Indicates that an entity includes or shows a depiction of a particular starship class.
-
D.
fighterType
Indicates the specific combat or fighting style category that an entity belongs to.
-
E.
usesStarshipClass
chosen
Indicates that an entity operates, employs, or is associated with a particular class or type of starship.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66388afe48190a68caf56c9745007 |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, noon