Triple
T25265293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Struma |
E633412
|
entity |
| Predicate | conditionAtVoyage |
P158077
|
FINISHED |
| Object | poor mechanical condition |
—
|
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: poor mechanical condition | Statement: [Struma, conditionAtVoyage, poor mechanical condition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionAtVoyage Context triple: [Struma, conditionAtVoyage, poor mechanical condition]
-
A.
surveyedDuringVoyageOf
Indicates that one entity was surveyed or examined in the course of a particular voyage undertaken by another entity.
-
B.
voyageOn
Indicates that an entity is traveling or being transported aboard a particular vessel or means of sea (or space) travel.
-
C.
statusDuringFinalVoyage
Indicates the role, condition, or state an entity held specifically during its final voyage.
-
D.
associatedWithVoyage
Indicates a relationship where an entity is linked or connected to a specific voyage, journey, or trip.
-
E.
voyageStatusAtSinking
Indicates the status or phase of a voyage that a vessel was in at the time it sank.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4839787908190a5fc04739139cee8 |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 1:14 p.m.