Triple
T27111180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dravidian cultural region |
E686715
|
entity |
| Predicate | hasNotableTempleCity |
P14082
|
FINISHED |
| Object | Madurai |
—
|
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: Madurai | Statement: [Dravidian cultural region, hasNotableTempleCity, Madurai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTempleCity Context triple: [Dravidian cultural region, hasNotableTempleCity, Madurai]
-
A.
hasNotableTemple
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
-
B.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
C.
hasTempleDistrict
Indicates that a place or settlement contains or is associated with a designated temple district area.
-
D.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
E.
hasNotableTown
chosen
Indicates that an entity includes or is associated with a town that is considered notable or significant in some way.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 27, 2026, 8:54 a.m.