Triple
T8219684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain City |
E192025
|
entity |
| Predicate | notableFeatureOfCity |
P46334
|
FINISHED |
| Object | dense high‑rise buildings on steep slopes |
—
|
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: dense high‑rise buildings on steep slopes | Statement: [Mountain City, notableFeatureOfCity, dense high‑rise buildings on steep slopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFeatureOfCity Context triple: [Mountain City, notableFeatureOfCity, dense high‑rise buildings on steep slopes]
-
A.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
B.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
C.
notableCityIncluded
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
D.
notableLocationFeature
chosen
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
E.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7772b76c8190b1952650c736eb91 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.