Triple
T12669262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise-D |
E302632
|
entity |
| Predicate | hasShuttlecraftType |
P106198
|
FINISHED |
| Object | Type 6 shuttlecraft |
—
|
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: Type 6 shuttlecraft | Statement: [USS Enterprise-D, hasShuttlecraftType, Type 6 shuttlecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShuttlecraftType Context triple: [USS Enterprise-D, hasShuttlecraftType, Type 6 shuttlecraft]
-
A.
hasShuttlecraft
Indicates that an entity possesses, controls, or is equipped with one or more shuttlecraft.
-
B.
hasShuttleBay
Indicates that an entity possesses or is equipped with a shuttle bay as part of its structure or facilities.
-
C.
isOnSpacecraftType
Indicates that one entity is currently aboard or assigned to a spacecraft of a specified type.
-
D.
hasLiftOrLaunchSystem
Indicates that an entity is equipped with, or associated with, a system used to lift, launch, or otherwise deploy another object or vehicle.
-
E.
usesSpacecraftVariant
Indicates that one entity employs or operates a specific variant or version of a spacecraft.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:20 p.m.