Triple
T21648301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psamtik I |
E534271
|
entity |
| Predicate | usedForeignTroops |
P14068
|
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: [Psamtik I, usedForeignTroops, Greek mercenaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForeignTroops Context triple: [Psamtik I, usedForeignTroops, Greek mercenaries]
-
A.
hasPeacekeepingForcesFrom
Indicates that an entity hosts or is supported by peacekeeping forces that originate from another specified entity.
-
B.
countryOfUSForces
Indicates that a given country is the nation in which United States military forces are present or operating.
-
C.
militaryInterventionBy
Indicates a situation where one actor carries out or participates in a military intervention directed toward or within another actor or territory.
-
D.
militaryForceUsed
chosen
Indicates that one entity employs or applies military power or armed force against, within, or in relation to another entity or situation.
-
E.
mayBeAwardedToForeignMilitary
Indicates that the award or honor can be conferred upon members of a foreign military force.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59124e1c81908d454894d66359e7 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.