Triple
T13414966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Misti |
E313187
|
entity |
| Predicate | hasHumanSettlementsOnFlanks |
P16159
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [El Misti, hasHumanSettlementsOnFlanks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanSettlementsOnFlanks Context triple: [El Misti, hasHumanSettlementsOnFlanks, yes]
-
A.
hasHumanSettlementAlong
Indicates that a human settlement is located adjacent to or distributed along the length of a specified geographic feature or route.
-
B.
hasHumanSettlement
chosen
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
C.
allianceFlank
Indicates a cooperative maneuver where allied entities position themselves on the side of a common target or objective to gain a tactical advantage.
-
D.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
E.
numberOfSettlersCaptured
Indicates the quantity of settlers who have been taken captive in a given context or event.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb6e904819098cc9153fd2feaf5 |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:39 p.m.