Triple
T25489410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhagavata Mela Natakam |
E638798
|
entity |
| Predicate | hasPrimaryStateAssociation |
P8944
|
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: [Bhagavata Mela Natakam, hasPrimaryStateAssociation, Tamil Nadu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryStateAssociation Context triple: [Bhagavata Mela Natakam, hasPrimaryStateAssociation, Tamil Nadu]
-
A.
hasPrimaryAssociation
Indicates that one entity is chiefly or most directly connected, linked, or related to another among possible associations.
-
B.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
C.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
D.
hasPrimaryAccessType
Indicates that an entity is associated with its main or default mode or category of access.
-
E.
hasPrimaryStateServed
chosen
Indicates that an entity has served or operated primarily within a specified state or state-level jurisdiction.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 21, 2026, 2:34 p.m.