Triple
T27646360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annamalaiyar |
E696721
|
entity |
| Predicate | hasRegionOfCult |
P285
|
FINISHED |
| Object | Tamil Nadu |
—
|
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: Tamil Nadu | Statement: [Annamalaiyar, hasRegionOfCult, Tamil Nadu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionOfCult Context triple: [Annamalaiyar, hasRegionOfCult, Tamil Nadu]
-
A.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
B.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
C.
isCulturalAreaFor
Indicates that one entity serves as a designated cultural area or space intended for the cultural activities, practices, or identity of another entity.
-
D.
hasCulturalPresenceOf
Indicates that something exhibits, contains, or is characterized by the cultural influence, activities, or representation of a particular group, tradition, or culture.
-
E.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: April 27, 2026, 2:29 p.m.