Triple
T15455115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clearchus of Sparta |
E371749
|
entity |
| Predicate | commandedForceType |
P95229
|
FINISHED |
| Object | Greek mercenaries |
—
|
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 mercenaries | Statement: [Clearchus of Sparta, commandedForceType, Greek mercenaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedForceType Context triple: [Clearchus of Sparta, commandedForceType, Greek mercenaries]
-
A.
commandedForcesOf
Indicates that one entity held command authority over the military or armed forces associated with another entity.
-
B.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
C.
enemyForceType
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
D.
commandedForcesAgainst
Indicates that one entity held command authority over military or armed forces engaged in opposition to another entity.
-
E.
typeOfUnitCommanded
chosen
Indicates the specific type or category of military or organizational unit that an entity is in command of.
- 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.