Triple
T21340621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Excelsior (NCC-2000) |
E526179
|
entity |
| Predicate | refitStatus |
P71588
|
FINISHED |
| Object | refitted to standard warp drive |
—
|
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: refitted to standard warp drive | Statement: [USS Excelsior (NCC-2000), refitStatus, refitted to standard warp drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refitStatus Context triple: [USS Excelsior (NCC-2000), refitStatus, refitted to standard warp drive]
-
A.
refit
Indicates that an existing object or structure is being modified, repaired, or equipped with new parts or features to restore or improve its function.
-
B.
reflaggedAs
Indicates that an entity has been assigned a new flag, status, or label, replacing or superseding its previous one.
-
C.
typeAfterRefit
chosen
Indicates that an entity’s type or classification after undergoing a refit or modification is the specified value.
-
D.
reconstructionStatus
Indicates the current state or phase of a reconstruction process that an entity is undergoing or has undergone.
-
E.
renewalStatus
Indicates the current state or outcome of a renewal process for an existing agreement, subscription, or status.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a84dfa04819097dbe21eb40a45ef |
completed | April 22, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:44 p.m.