Triple
T7834498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehrangarh Fort |
E181656
|
entity |
| Predicate | heightAboveCity |
P38170
|
FINISHED |
| Object | approximately 120 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 120 meters | Statement: [Mehrangarh Fort, heightAboveCity, approximately 120 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightAboveCity Context triple: [Mehrangarh Fort, heightAboveCity, approximately 120 meters]
-
A.
relativeHeightAboveCity
chosen
Indicates the vertical height of an entity measured above the reference elevation level of a specified city.
-
B.
heightAboveGround
Indicates the vertical distance of an entity measured from the ground surface directly beneath it.
-
C.
rankInCityByHeight
Indicates the relative ordering of entities within a specific city based on their height, such as which is tallest, second tallest, and so on.
-
D.
buildingHeightContext
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
-
E.
heightAboveSurroundings
Indicates that an entity’s vertical position or elevation is higher than that of its immediate surrounding area.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb064b872081908e269f4fe1b85436 |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:45 p.m.