Triple
T5065876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pila |
E114142
|
entity |
| Predicate | hasApproximateBaseElevation |
P45909
|
FINISHED |
| Object | about 1800 meters |
—
|
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: about 1800 meters | Statement: [Pila, hasApproximateBaseElevation, about 1800 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateBaseElevation Context triple: [Pila, hasApproximateBaseElevation, about 1800 meters]
-
A.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
-
B.
elevationApproxMeters
chosen
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
C.
elevationAtBase
Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference level.
-
D.
hasAverageElevation
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749aceac8190817278266308fd64 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.