Triple
T15817433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varyag |
E383514
|
entity |
| Predicate | scuttledYear |
P7070
|
FINISHED |
| Object | 1904 |
—
|
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: 1904 | Statement: [Varyag, scuttledYear, 1904]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scuttledYear Context triple: [Varyag, scuttledYear, 1904]
-
A.
scuttledAfter
Indicates that one entity was deliberately sunk or rendered inoperable after the occurrence or completion of another specified event or action.
-
B.
yearOfSinking
chosen
Indicates the specific calendar year in which an entity (typically a vessel or structure) sank.
-
C.
scuttlingOrderedBy
Indicates that one entity ordered, directed, or authorized the scuttling (intentional sinking or disabling) of another entity.
-
D.
dateOfSinking
Indicates the specific calendar date on which an entity (typically a vessel or structure) sank.
-
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.
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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a4332c8190bc525e06d6f3a6b4 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.