Triple
T27914978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RZ-2 A-wing interceptor |
E706043
|
entity |
| Predicate | hyperdrive |
P163770
|
FINISHED |
| Object | equipped |
—
|
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: equipped | Statement: [RZ-2 A-wing interceptor, hyperdrive, equipped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hyperdrive Context triple: [RZ-2 A-wing interceptor, hyperdrive, equipped]
-
A.
hyperdriveRating
Indicates the performance or capability level of an entity’s hyperdrive system, typically reflecting its speed or efficiency relative to a standard.
-
B.
hypercharge
Indicates the relationship where a particle is assigned or characterized by its hypercharge, a quantum number related to its electroweak interaction properties.
-
C.
warpDrivePioneer
Indicates that an entity is recognized as having been among the first to develop, invent, or successfully use warp drive technology.
-
D.
spaceflownWith
Indicates that two entities have traveled together in space on the same spaceflight or mission.
-
E.
reentryVehicle
Indicates that an entity functions as a vehicle designed to re-enter an atmosphere from space.
- F. None of above. chosen
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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:53 p.m.