Triple
T4182574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lechaeum |
E88226
|
entity |
| Predicate | smallerForce |
P24324
|
FINISHED |
| Object | Athenian force |
—
|
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: Athenian force | Statement: [Battle of Lechaeum, smallerForce, Athenian force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smallerForce Context triple: [Battle of Lechaeum, smallerForce, Athenian force]
-
A.
isSmallForce
Indicates that the force involved has a relatively low magnitude compared to typical or relevant reference forces.
-
B.
weakerThan
chosen
Indicates that one entity has less strength, power, or effectiveness than another entity.
-
C.
forceSize
Indicates a relationship where one entity specifies or constrains the magnitude or size of a force associated with another entity.
-
D.
associatedForce
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that entity.
-
E.
primaryForce
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.