Triple
T6484174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinano |
E146466
|
entity |
| Predicate | constructionStatusAtSinking |
P71190
|
FINISHED |
| Object | not fully completed |
—
|
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: not fully completed | Statement: [Shinano, constructionStatusAtSinking, not fully completed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionStatusAtSinking Context triple: [Shinano, constructionStatusAtSinking, not fully completed]
-
A.
wreckStatus
Indicates the condition or state of damage of an object, typically describing whether and how badly it has been wrecked.
-
B.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
-
C.
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.
-
D.
sankOnMaidenVoyage
Indicates that the subject vessel sank during its very first voyage.
-
E.
sankOn
Indicates that one entity moved downward and became submerged or lower in level relative to another entity or reference point.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a6de31c81909dd99d105f5bb4c2 |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c06822f73081908e6bb9edecbe77a6 |
completed | March 22, 2026, 10:07 p.m. |
Created at: March 22, 2026, 4:52 p.m.