Triple
T3200197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Challenger |
E67030
|
entity |
| Predicate | endTimeOfUseAsResearchVessel |
P46090
|
FINISHED |
| Object | 1876 |
—
|
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: 1876 | Statement: [HMS Challenger, endTimeOfUseAsResearchVessel, 1876]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeOfUseAsResearchVessel Context triple: [HMS Challenger, endTimeOfUseAsResearchVessel, 1876]
-
A.
decommissionedAsWorkingVessel
Indicates that an entity has been officially retired from service and is no longer used as an active working vessel.
-
B.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
C.
undockingDate
Indicates the date on which one object or vehicle separates and moves away from another to which it was previously docked.
-
D.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
E.
militaryUseEnd
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9ad4b1c8190bc6ad0f025f238c8 |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.