Triple
T29202013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiruvannamalai |
E740302
|
entity |
| Predicate | hasHillHeight |
P193120
|
FINISHED |
| Object | Arunachala about 814 metres above sea level |
—
|
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: Arunachala about 814 metres above sea level | Statement: [Tiruvannamalai, hasHillHeight, Arunachala about 814 metres above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHillHeight Context triple: [Tiruvannamalai, hasHillHeight, Arunachala about 814 metres above sea level]
-
A.
hasHillSize
Indicates that something possesses or is characterized by a particular hill size.
-
B.
containsHill
Indicates that one entity geographically includes or encompasses a hill within its area or boundaries.
-
C.
isHill
Indicates that the subject entity is classified as a hill, i.e., a naturally raised area of land lower and less steep than a mountain.
-
D.
hasApproximateNumberOfHills
Indicates that an entity is associated with an estimated or imprecise count of hills rather than an exact number.
-
E.
hasHillDesignation
Indicates that an entity is assigned a specific designation or status related to a hill.
- F. None of above. chosen
Provenance (4 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 28, 2026, 12:07 p.m.