Triple
T17917508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churcampa Province |
E447970
|
entity |
| Predicate | partOfRegionType |
P1828
|
FINISHED |
| Object | Andean region |
—
|
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: Andean region | Statement: [Churcampa Province, partOfRegionType, Andean region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfRegionType Context triple: [Churcampa Province, partOfRegionType, Andean region]
-
A.
regionalType
Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
-
B.
regionType
chosen
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
C.
typicalRegionType
Indicates that a region is of a characteristic or commonly occurring type for a given context or entity.
-
D.
partOfPlanningRegion
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
E.
partOfResourceRegion
Indicates that one resource is contained within, or forms a component of, a larger resource-defined region.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30778fc81908b5b2e308fb158a5 |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:20 a.m.