Triple
T552386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Jutland |
E11867
|
entity |
| Predicate | tacticalOutcome |
P15636
|
FINISHED |
| Object | inconclusive |
—
|
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: inconclusive | Statement: [Battle of Jutland, tacticalOutcome, inconclusive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticalOutcome Context triple: [Battle of Jutland, tacticalOutcome, inconclusive]
-
A.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
C.
typeOfVictory
Indicates the specific manner or category in which a victory was achieved.
-
D.
historicalOutcome
Indicates the result or consequence that an event, action, or situation produced in a historical context.
-
E.
subsequentOutcomeForWinner
Indicates that the predicate links a winner to an outcome or event that occurs to or for them after their initial victory.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499047bd4819089ca8345f1b6e46c |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.