Triple
T38368571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-1 starfighter |
E892517
|
entity |
| Predicate | astromechSocket |
P61803
|
FINISHED |
| Object | 1 astromech droid |
—
|
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: 1 astromech droid | Statement: [N-1 starfighter, astromechSocket, 1 astromech droid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astromechSocket Context triple: [N-1 starfighter, astromechSocket, 1 astromech droid]
-
A.
occursOnStarship
Indicates that an event or action takes place aboard or within a starship.
-
B.
usedOnStarships
chosen
Indicates that something is employed or applied in the context of starships, such as equipment, technology, or materials used aboard or for operating them.
-
C.
usesStarfighter
Indicates that one entity operates or employs a starfighter as its vehicle, tool, or means of transportation or combat.
-
D.
notableStarfighter
Indicates that an entity is a starfighter recognized for particular significance, prominence, or distinction (e.g., historically, tactically, or culturally).
-
E.
hasStarship
Indicates that one entity possesses, controls, or is associated with a particular 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.