Triple
T22458282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanyakumari Beach |
E555168
|
entity |
| Predicate | locatedAtSouthernmostTipOf |
P17679
|
FINISHED |
| Object | mainland India |
—
|
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: mainland India | Statement: [Kanyakumari Beach, locatedAtSouthernmostTipOf, mainland India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtSouthernmostTipOf Context triple: [Kanyakumari Beach, locatedAtSouthernmostTipOf, mainland India]
-
A.
isSouthernmostPartOf
chosen
Indicates that one entity is the geographically furthest south portion or section of another entity.
-
B.
southernmost
Indicates that one entity is located farther to the south than all other comparable entities in a given set or context.
-
C.
southernmostInhabitedIslandOf
Indicates that one island is the southernmost inhabited island within the territory, region, or jurisdiction of another entity.
-
D.
southernmostDistrictOf
Indicates that one district is the geographically furthest south within the boundaries of a specified larger region or entity.
-
E.
southernmostCityOf
Indicates that one city is the geographically furthest south among all cities within a specified region or set.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b7d00208190955a70e2c22d25a4 |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.