Triple
T25389177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saite kingdom |
E631610
|
entity |
| Predicate | allowedSettlementOf |
P164986
|
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: [Saite kingdom, allowedSettlementOf, Greek mercenaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedSettlementOf Context triple: [Saite kingdom, allowedSettlementOf, Greek mercenaries]
-
A.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
-
B.
isSettlementOf
Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
-
C.
settlementAct
Indicates the act of resolving a dispute or obligation, typically by reaching and formalizing a settlement between involved parties.
-
D.
settledAs
Indicates that one entity has been resolved, finalized, or agreed upon in the form or status of another entity.
-
E.
possibleSettlementAt
Indicates that a settlement could potentially be established or located at a given place or site.
- F. None of above. chosen
Provenance (4 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 21, 2026, 1:47 p.m.