Triple
T20839610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yathothkari Perumal Temple |
E513056
|
entity |
| Predicate | cityTypeLocation |
P142042
|
FINISHED |
| Object | temple city of Kanchipuram |
—
|
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: temple city of Kanchipuram | Statement: [Yathothkari Perumal Temple, cityTypeLocation, temple city of Kanchipuram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityTypeLocation Context triple: [Yathothkari Perumal Temple, cityTypeLocation, temple city of Kanchipuram]
-
A.
cityLocation
Indicates that a city is geographically situated within or associated with a specific larger area or place.
-
B.
cityLocatedIn
Indicates that a city is geographically situated within a specified larger administrative or territorial region.
-
C.
cityOn
Indicates that a city is geographically located on a specified landform, area, or administrative region.
-
D.
cityName
Indicates that the associated value is the name of a city.
-
E.
cityIs
Indicates that one entity is a city associated with, or identified as, another entity.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34a60848190b33078172675f8d7 |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:42 p.m.