Triple
T36164132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uitikon |
E1045950
|
entity |
| Predicate | locatedOnHillRange |
P61494
|
FINISHED |
| Object | Uetliberg area |
—
|
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: Uetliberg area | Statement: [Uitikon, locatedOnHillRange, Uetliberg area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnHillRange Context triple: [Uitikon, locatedOnHillRange, Uetliberg area]
-
A.
locatedInHills
chosen
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
-
B.
locatedOnPeak
Indicates that one entity is situated at or on the summit or highest point of another entity (a peak).
-
C.
locatedInMountainRangeRegion
Indicates that a place or geographic entity is situated within the area covered by a specific mountain range.
-
D.
locatedInMountainSubrange
Indicates that one mountain or geographic feature is situated within a specific subrange of a larger mountain range.
-
E.
isAssociatedWithHill
Indicates a relationship where an entity is connected or related in some notable way to a hill.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.