Triple
T34775013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranapiacaba region |
E1002477
|
entity |
| Predicate | elevationRangeApproxM |
P1977
|
FINISHED |
| Object | around 750–900 |
—
|
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: around 750–900 | Statement: [Paranapiacaba region, elevationRangeApproxM, around 750–900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationRangeApproxM Context triple: [Paranapiacaba region, elevationRangeApproxM, around 750–900]
-
A.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
B.
typicalElevationRange
chosen
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
C.
elevationMinApprox
Indicates an approximate value for the minimum elevation associated with an entity or location.
-
D.
elevationCoverageApproximate
Indicates an approximate or estimated representation of how elevation values are covered or distributed over a given area or dataset.
-
E.
elevationFeetApproximate
Indicates the approximate elevation of an entity above sea level, measured in feet.
- 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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 3:59 p.m.