Triple
T6954639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Orville (ECV-197) |
E161210
|
entity |
| Predicate | operationalStatusInSeries |
P5870
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [USS Orville (ECV-197), operationalStatusInSeries, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalStatusInSeries Context triple: [USS Orville (ECV-197), operationalStatusInSeries, active]
-
A.
operatingStatus
chosen
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
B.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
C.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
D.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
E.
chainOfCommandStatus
Indicates the position or state of an entity within a hierarchical authority or command structure, including who they report to or have authority over.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dace1a94819095311e4288f01784 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.