Triple
T29362656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theed Royal Hangar |
E744630
|
entity |
| Predicate | associatedStarfighter |
P108461
|
FINISHED |
| Object | Naboo N-1 starfighter |
E892517
|
NE 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: Naboo N-1 starfighter | Statement: [Theed Royal Hangar, associatedStarfighter, Naboo N-1 starfighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStarfighter Context triple: [Theed Royal Hangar, associatedStarfighter, Naboo N-1 starfighter]
-
A.
notableStarfighter
Indicates that an entity is a starfighter recognized for particular significance, prominence, or distinction (e.g., historically, tactically, or culturally).
-
B.
usesStarfighter
Indicates that one entity operates or employs a starfighter as its vehicle, tool, or means of transportation or combat.
-
C.
hasStarshipClassDepicted
Indicates that an entity includes or shows a depiction of a particular starship class.
-
D.
occursOnStarship
Indicates that an event or action takes place aboard or within a starship.
-
E.
hasStarship
chosen
Indicates that one entity possesses, controls, or is associated with a particular starship.
- F. None of above.
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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a036054129081909e66c5d62015e6c1 |
completed | May 12, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2757d9060c819088686744787d7e08 |
completed | June 9, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a035f17cbf88190acd6bdbfc9789ffb |
completed | May 12, 2026, 5:10 p.m. |
Created at: April 28, 2026, 2:19 p.m.