Triple
T15455125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clearchus of Sparta |
E371749
|
entity |
| Predicate | armyComponentCommanded |
P87506
|
FINISHED |
| Object | Greek heavy infantry |
—
|
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: Greek heavy infantry | Statement: [Clearchus of Sparta, armyComponentCommanded, Greek heavy infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armyComponentCommanded Context triple: [Clearchus of Sparta, armyComponentCommanded, Greek heavy infantry]
-
A.
hasMilitaryUnitTypeCommanded
chosen
Indicates that a person or entity has commanded a military unit of a specified type (e.g., battalion, brigade, division).
-
B.
commandedForcesOf
Indicates that one entity held command authority over the military or armed forces associated with another entity.
-
C.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
D.
numberOfUnitsCommanded
Indicates the quantity of units that an entity is in command of within a given context.
-
E.
garrisonCommand
Indicates that one entity holds command authority over the garrison or stationed military forces at a particular location.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f146a2c8190882741af3ec15268 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:31 a.m.