Triple
T35984924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zev Senesca |
E1040682
|
entity |
| Predicate | flewStarfighterType |
P80075
|
FINISHED |
| Object | T-47 airspeeder |
—
|
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: T-47 airspeeder | Statement: [Zev Senesca, flewStarfighterType, T-47 airspeeder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flewStarfighterType Context triple: [Zev Senesca, flewStarfighterType, T-47 airspeeder]
-
A.
usesStarfighter
chosen
Indicates that one entity operates or employs a starfighter as its vehicle, tool, or means of transportation or combat.
-
B.
fighterType
Indicates the specific combat or fighting style category that an entity belongs to.
-
C.
notableStarfighter
Indicates that an entity is a starfighter recognized for particular significance, prominence, or distinction (e.g., historically, tactically, or culturally).
-
D.
fighter1
Indicates that the subject is the first participant or primary combatant in a fight or competitive physical confrontation.
-
E.
hasStarshipClassDepicted
Indicates that an entity includes or shows a depiction of a particular starship class.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.