Triple
T2002945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coudenberg |
E43511
|
entity |
| Predicate | elevationAboveSurroundings |
P6557
|
FINISHED |
| Object | hilltop |
—
|
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: hilltop | Statement: [Coudenberg, elevationAboveSurroundings, hilltop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationAboveSurroundings Context triple: [Coudenberg, elevationAboveSurroundings, hilltop]
-
A.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
B.
elevationType
chosen
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
C.
topographicProminence
Indicates the height of a peak’s summit relative to the lowest contour line encircling it and no higher summit, expressing how much it stands out from surrounding terrain.
-
D.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
E.
hasAverageElevation
Indicates that an entity is characterized by a specific mean height above a defined 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8820cec8190a945e5daeb8c9df6 |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.