Triple
T10187875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS König |
E236956
|
entity |
| Predicate | battleLineRole |
P54516
|
FINISHED |
| Object | flagship of III Battle Squadron (at times) |
—
|
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: flagship of III Battle Squadron (at times) | Statement: [SMS König, battleLineRole, flagship of III Battle Squadron (at times)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleLineRole Context triple: [SMS König, battleLineRole, flagship of III Battle Squadron (at times)]
-
A.
battleOutcomeRole
Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
-
B.
frontlineRole
chosen
Indicates that an entity serves in a primary, direct-contact position at the forefront of an activity, operation, or service.
-
C.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
D.
roleInCombatSystem
Indicates the specific function or responsibility an entity has within a combat or battle mechanics framework.
-
E.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7a7aac8190af8dcb8374e62d68 |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.