Triple
T16254621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Maheno |
E394596
|
entity |
| Predicate | hospitalShipServiceEnd |
P122363
|
FINISHED |
| Object | 1919 |
—
|
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: 1919 | Statement: [SS Maheno, hospitalShipServiceEnd, 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hospitalShipServiceEnd Context triple: [SS Maheno, hospitalShipServiceEnd, 1919]
-
A.
enteredServiceAsHospitalShip
Indicates that an entity began operating in the role or capacity of a hospital ship from a specified point in time.
-
B.
hospitalFunction
Indicates the specific medical or administrative role, service, or operational purpose that a hospital performs.
-
C.
containsHospital
Indicates that one entity includes or encompasses a hospital within its boundaries or composition.
-
D.
hospitalLocation
Indicates the geographic place or address where a hospital is situated.
-
E.
hasDischarge
Indicates that one entity releases, emits, or expels a substance, energy, or flow from itself.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24599861881908b9235f005d80a96 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.