Triple
T15354286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xingu Indigenous Park |
E367134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national park-level reserve |
C35964
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: national park-level reserve Context triple: [Xingu Indigenous Park, instanceOf, national park-level reserve]
-
A.
national park area
A national park area is a protected geographic region designated by a government to conserve natural landscapes, ecosystems, and wildlife while providing opportunities for public recreation and education.
-
B.
National Historical Reserve
A National Historical Reserve is a protected area that preserves and interprets a significant concentration of historical sites, landscapes, and cultural resources under coordinated management for education, research, and public enjoyment.
-
C.
nature reserve
A nature reserve is a protected area of land or water designated to conserve wildlife, habitats, and natural features, often limiting human activities to research, education, and low-impact recreation.
-
D.
quasi-national park
A quasi-national park is a protected natural area designated and managed by regional or local authorities, offering conservation and recreation functions similar to a national park but with a lower or more flexible legal status.
-
E.
National Scenic Area
A National Scenic Area is a designated region recognized and protected for its outstanding natural beauty, distinctive landscapes, and cultural or recreational value, managed to conserve its character while allowing compatible public enjoyment and sustainable use.
- F. None of above. chosen
Provenance (1 batch)
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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:18 a.m.