Triple
T25446440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palani Hills |
E637648
|
entity |
| Predicate | hasHighestTown |
P847
|
FINISHED |
| Object | Kodaikanal |
—
|
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: Kodaikanal | Statement: [Palani Hills, hasHighestTown, Kodaikanal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestTown Context triple: [Palani Hills, hasHighestTown, Kodaikanal]
-
A.
hasHighestCity
Indicates that one entity possesses or contains the city with the greatest value according to some ranking criterion (e.g., highest population, elevation, or status) among a set of cities.
-
B.
highestMarketTownIn
Indicates that a town is the highest-elevation market town located within a specified area or region.
-
C.
isLargestTownOn
Indicates that one town is the largest (by size, population, or another defined measure) among all towns located on a specified geographic feature or area.
-
D.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
E.
hasTown
chosen
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 2:02 p.m.