Triple
T13111932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Artemisium |
E310992
|
entity |
| Predicate | GreekStrategy |
P108103
|
FINISHED |
| Object | defensive naval stand |
—
|
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: defensive naval stand | Statement: [Battle of Artemisium, GreekStrategy, defensive naval stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GreekStrategy Context triple: [Battle of Artemisium, GreekStrategy, defensive naval stand]
-
A.
GreekForcesIncluded
Indicates that a set of forces or troops includes Greek military units as part of its composition.
-
B.
goalInTrojanWar
Indicates that an entity’s objective, aim, or purpose is specifically directed toward or realized within the context of the Trojan War.
-
C.
PersianTactics
Indicates the use or application of military strategies, maneuvers, or methods characteristic of Persian forces in a conflict or battle context.
-
D.
PonticCommander
Indicates a person who holds a commanding military role within the forces of Pontus or a Pontic polity.
-
E.
roleInBattleOfSalamis
Indicates the specific role or involvement an entity had in the Battle of Salamis.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817e4f408190b77c198b4157d77a |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:05 p.m.