Triple
T38368582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-1 starfighter |
E892517
|
entity |
| Predicate | notableAstromech |
P204619
|
FINISHED |
| Object | R2-D2 |
E205720
|
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: R2-D2 | Statement: [N-1 starfighter, notableAstromech, R2-D2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAstromech Context triple: [N-1 starfighter, notableAstromech, R2-D2]
-
A.
notableStarfighter
Indicates that an entity is a starfighter recognized for particular significance, prominence, or distinction (e.g., historically, tactically, or culturally).
-
B.
hasStarshipClassDepicted
Indicates that an entity includes or shows a depiction of a particular starship class.
-
C.
occursOnStarship
Indicates that an event or action takes place aboard or within a starship.
-
D.
notableOrbiter
Indicates that one entity is a particularly significant or well-known artificial satellite or spacecraft that orbits another entity.
-
E.
usedOnStarships
Indicates that something is employed or applied in the context of starships, such as equipment, technology, or materials used aboard or for operating them.
- F. None of above. chosen
Provenance (5 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_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41a7d82dc88190920147321e81ea95 |
completed | June 28, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.