Triple
T1558794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sinop |
E33269
|
entity |
| Predicate | shipTypeUsedByRussia |
P8971
|
FINISHED |
| Object | ships of the line |
—
|
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: ships of the line | Statement: [Battle of Sinop, shipTypeUsedByRussia, ships of the line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipTypeUsedByRussia Context triple: [Battle of Sinop, shipTypeUsedByRussia, ships of the line]
-
A.
shipTypeInvolved
chosen
Indicates that a particular type or class of ship is involved or participates in a specified event, situation, or relationship.
-
B.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
C.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
D.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
E.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:27 p.m.