Triple
T35731601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toraja coffee |
E1032764
|
entity |
| Predicate | growingAltitude |
P21269
|
FINISHED |
| Object | approximately 1000–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: approximately 1000–1800 meters | Statement: [Toraja coffee, growingAltitude, approximately 1000–1800 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: growingAltitude Context triple: [Toraja coffee, growingAltitude, approximately 1000–1800 meters]
-
A.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
B.
isHighElevation
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
C.
altitudeEffect
Indicates how a change in altitude influences or modifies some property, condition, or outcome.
-
D.
campElevation
Indicates the elevation or height above sea level at which a camp is located.
-
E.
locatedAtAltitude
chosen
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.