Triple
T13111933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Artemisium |
E310992
|
entity |
| Predicate | PersianStrategy |
P49548
|
FINISHED |
| Object | use of numerically superior fleet |
—
|
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: use of numerically superior fleet | Statement: [Battle of Artemisium, PersianStrategy, use of numerically superior fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PersianStrategy Context triple: [Battle of Artemisium, PersianStrategy, use of numerically superior fleet]
-
A.
PersianTactics
chosen
Indicates the use or application of military strategies, maneuvers, or methods characteristic of Persian forces in a conflict or battle context.
-
B.
PersianCommander
Indicates that an entity serves as a military commander for, or in the context of, the Persian forces or Persian polity.
-
C.
PersianForceComponent
Indicates that an entity functions as a constituent unit or sub-force within a larger Persian military force or formation.
-
D.
ParthianForceType
Indicates the type or classification of a military force associated with the Parthians.
-
E.
sideSasanian
Indicates that an entity is aligned with, belongs to, or is on the side of the Sasanian faction or polity in a given 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_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. |
Created at: April 9, 2026, 9:05 p.m.