Triple
T22196719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maipo Andes |
E548567
|
entity |
| Predicate | subregionType |
P146803
|
FINISHED |
| Object | Andean sector of Maipo Valley |
—
|
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 sector of Maipo Valley | Statement: [Maipo Andes, subregionType, Andean sector of Maipo Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subregionType Context triple: [Maipo Andes, subregionType, Andean sector of Maipo Valley]
-
A.
regionalType
Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
-
B.
subregionOf
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
-
C.
regionSub
Indicates that one region is a subregion or contained part of another, larger region.
-
D.
countrySubregion
Indicates that a country is located within or belongs to a specific subregion of the world.
-
E.
countrySubdivisionType
Indicates the specific type or category of an administrative or territorial subdivision within a country (e.g., state, province, region).
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae7c72081909b7817d66391bef4 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:35 p.m.