Triple
T12917110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise-B |
E309012
|
entity |
| Predicate | shieldsStatusOnLaunch |
P107006
|
FINISHED |
| Object | shields not fully configured on maiden voyage |
—
|
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: shields not fully configured on maiden voyage | Statement: [USS Enterprise-B, shieldsStatusOnLaunch, shields not fully configured on maiden voyage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shieldsStatusOnLaunch Context triple: [USS Enterprise-B, shieldsStatusOnLaunch, shields not fully configured on maiden voyage]
-
A.
featuresShield
Indicates that an entity includes or is equipped with a shield as one of its characteristics or components.
-
B.
shieldPresent
Indicates that a protective shield is currently active or available in the given context.
-
C.
ShieldsSide
Indicates that one entity is positioned or aligned on a particular side of another entity’s shield.
-
D.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
E.
startingGuard
Indicates that an entity serves as the primary or first-choice guard in a lineup, formation, or configuration.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a1e8088190af697629baecf59f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9708a86bc8190bcdcf97e845bb413 |
completed | April 10, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:41 p.m.