Triple
T25168015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Preston |
E630234
|
entity |
| Predicate | shipMalfunction |
P157983
|
FINISHED |
| Object | pod malfunction causes early awakening |
—
|
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: pod malfunction causes early awakening | Statement: [Jim Preston, shipMalfunction, pod malfunction causes early awakening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipMalfunction Context triple: [Jim Preston, shipMalfunction, pod malfunction causes early awakening]
-
A.
shipInvolved
Indicates that a ship participates in, is associated with, or plays a role in a specified event or situation.
-
B.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
C.
shipwreckUse
Indicates that an entity makes use of, interacts with, or derives benefit from a shipwreck.
-
D.
shipFunction
Indicates that one entity serves as the functional role, purpose, or operational use of a ship.
-
E.
shipDraft
Indicates the depth of a ship’s hull below the waterline, typically representing how deeply the vessel sits in the water.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d43e6d08190bbd8643ea058ceea |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
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, 12:18 p.m.