Triple
T3591267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athenian navy |
E76029
|
entity |
| Predicate | tacticalDoctrine |
P30685
|
FINISHED |
| Object | ramming tactics |
—
|
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: ramming tactics | Statement: [Athenian navy, tacticalDoctrine, ramming tactics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticalDoctrine Context triple: [Athenian navy, tacticalDoctrine, ramming tactics]
-
A.
militaryDoctrine
Indicates that one entity embodies, follows, or defines the strategic military principles, tactics, and operational guidelines used by another entity.
-
B.
militaryStrategy
Indicates a relationship where an entity plans, directs, or is associated with the organized use of armed forces and tactics to achieve military or defense objectives.
-
C.
militaryTacticsUsed
chosen
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
D.
tacticalFormation
Indicates a specific strategic arrangement or positioning of entities relative to one another to achieve a tactical objective.
-
E.
militaryTacticsFaced
Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1581278819081dd73b4c71e422e |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.