Triple
T19396820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxapampa Province |
E485211
|
entity |
| Predicate | hasSettlementFoundedBy |
P66111
|
FINISHED |
| Object | Austrian settlers |
—
|
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: Austrian settlers | Statement: [Oxapampa Province, hasSettlementFoundedBy, Austrian settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementFoundedBy Context triple: [Oxapampa Province, hasSettlementFoundedBy, Austrian settlers]
-
A.
possiblyFoundedBy
Indicates that an entity may have been founded or established by another entity, but this founding relationship is uncertain or not definitively confirmed.
-
B.
originOfSettlement
Indicates the place, source, or starting point from which a settlement was established or originated.
-
C.
settlerOf
chosen
Indicates that an entity established or inhabited a place as a settler of that location.
-
D.
realmFoundedBy
Indicates that a particular realm or domain was established or created by a specific founding entity.
-
E.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62573f5788190a635b92121db2cf7 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.