Triple
T22426178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athenian Empire |
E554373
|
entity |
| Predicate | mainMilitaryStrength |
P104865
|
FINISHED |
| Object | navy |
—
|
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: navy | Statement: [Athenian Empire, mainMilitaryStrength, navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainMilitaryStrength Context triple: [Athenian Empire, mainMilitaryStrength, navy]
-
A.
warPower
Indicates the authority, capability, or legal power to initiate, conduct, or manage acts of war or armed conflict.
-
B.
hasArmedForces
chosen
Indicates that an entity possesses or maintains organized military forces under its control.
-
C.
warTimeStrengthApprox
Indicates an approximate measure of an entity’s military strength or capacity during a time of war.
-
D.
militaryEquivalence
Indicates that two or more entities possess comparable military capabilities, strength, or strategic power such that neither holds a clear military advantage over the other.
-
E.
strengthGovernmentForces
Indicates the level or degree of military or coercive power held or exerted by government forces 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2d4dd88190a156c24b02b1591b |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.