Triple
T29211055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civaka Cintamani Kaviyam |
E740546
|
entity |
| Predicate | originatesInRegion |
P33091
|
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: [Civaka Cintamani Kaviyam, originatesInRegion, Tamil Nadu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesInRegion Context triple: [Civaka Cintamani Kaviyam, originatesInRegion, Tamil Nadu]
-
A.
isFromRegion
chosen
Indicates that one entity originates from, is associated with, or belongs to a specified geographic region.
-
B.
administrativeRegionOfOrigin
Indicates the administrative region (such as a state, province, or similar division) from which an entity originates or is associated by origin.
-
C.
sourceRegion
Indicates the geographic or spatial region from which something originates or is derived.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: April 28, 2026, 12:11 p.m.