Triple
T6954633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Orville (ECV-197) |
E161210
|
entity |
| Predicate | hasSickbay |
P10262
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [USS Orville (ECV-197), hasSickbay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSickbay Context triple: [USS Orville (ECV-197), hasSickbay, yes]
-
A.
hasMedicalCenter
chosen
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
-
B.
containsHospital
Indicates that one entity includes or encompasses a hospital within its boundaries or composition.
-
C.
hospitalizedIn
Indicates that a person or patient is admitted for medical care and staying as an inpatient in a specified hospital or healthcare facility.
-
D.
designatedAsFlagshipHospitalFor
Indicates that one hospital has been officially selected or recognized as the primary or leading flagship institution for another entity (such as a health system, region, or organization).
-
E.
hasClinicalUnit
Indicates that an entity is associated with or belongs to a specific clinical unit or department within a healthcare setting.
- 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.