Triple
T26840144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udhagamandalam |
E675754
|
entity |
| Predicate | famousPlace |
P7335
|
FINISHED |
| Object | Ooty Lake |
—
|
NE NERFINISHED |
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: Ooty Lake | Statement: [Udhagamandalam, famousPlace, Ooty Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousPlace Context triple: [Udhagamandalam, famousPlace, Ooty Lake]
-
A.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
B.
touristAttractionIn
chosen
Indicates that a place functions as a tourist attraction located within a specified geographic area or entity.
-
C.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
D.
cityLandmarkID
Indicates that a specific landmark is uniquely identified as being located within a particular city.
-
E.
alsoAttractsTouristsIn
Indicates that a place, in addition to another, draws or appeals to tourists within a specified location or context.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 5:07 a.m.