Triple
T36044650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Chicora |
E1042634
|
entity |
| Predicate | sinkingStatus |
P184505
|
FINISHED |
| Object | mysterious sinking |
—
|
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: mysterious sinking | Statement: [SS Chicora, sinkingStatus, mysterious sinking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sinkingStatus Context triple: [SS Chicora, sinkingStatus, mysterious sinking]
-
A.
sunkAs
Indicates that one entity caused another entity to sink or become submerged, typically resulting in its loss or destruction.
-
B.
voyageStatusAtSinking
Indicates the status or phase of a voyage that a vessel was in at the time it sank.
-
C.
sunk
Indicates that one entity caused another entity to go below the surface of a liquid, typically water, so that it is submerged or destroyed.
-
D.
sankWhile
Indicates that one entity moved downward below a surface or level at the same time that another specified event or action was occurring.
-
E.
sunkDuring
Indicates that one entity was sunk in the course of, or as a result of, the event or time period represented by another entity.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b35e32d481909ef0220e6f6ff4a8 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2c66054819083897e25edb65ba7 |
completed | May 3, 2026, 8:40 p.m. |
Created at: May 3, 2026, 4:07 p.m.