Triple
T29703091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Thetis |
E751543
|
entity |
| Predicate | incidentKnownAs |
P120113
|
FINISHED |
| Object | Thetis disaster |
—
|
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: Thetis disaster | Statement: [HMS Thetis, incidentKnownAs, Thetis disaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incidentKnownAs Context triple: [HMS Thetis, incidentKnownAs, Thetis disaster]
-
A.
incidentName
chosen
Indicates the specific name or label assigned to an incident within a system or context.
-
B.
incidentWith
Indicates that one entity is involved in, affected by, or associated with a particular incident or event together with another entity.
-
C.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
D.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
E.
notableStoryEvent
Indicates that an event plays a significant or memorable role within the narrative or storyline associated with the subject.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672b5fcf88190b3f6b1d57529ea8a |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:25 p.m.