Triple
T14501624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corinthian navy |
E340154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek navy |
C31291
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ancient Greek navy Context triple: [Corinthian navy, instanceOf, ancient Greek navy]
-
A.
Byzantine warship
A Byzantine warship is a fast, oared and sailed naval vessel of the Eastern Roman (Byzantine) Empire, typically equipped with a ram and siphons for projecting Greek fire, designed for coastal defense, convoy escort, and Mediterranean sea control.
-
B.
ancient Greek military force
chosen
An ancient Greek military force is an organized body of citizen-soldiers, often centered around the hoplite phalanx and supported by various specialized units, mobilized by a polis or coalition to conduct warfare and defend its political interests.
-
C.
ancient Greek war
Ancient Greek war encompasses the organized, often city-state-driven conflicts of classical Greece, characterized by hoplite phalanxes, naval battles like those at Salamis, shifting alliances, and a fusion of military, political, and cultural motives.
-
D.
ancient Greek alliance
An ancient Greek alliance is a formal coalition of independent city-states that coordinate their military, political, and sometimes economic actions for mutual defense or shared objectives.
-
E.
Athenian-led coalition
An Athenian-led coalition is an alliance of city-states or political entities organized under the leadership and strategic direction of Athens to pursue shared military, political, or economic objectives.
- F. None of above.
Provenance (1 batch)
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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:21 a.m.