Triple
T25282262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Thai |
E633851
|
entity |
| Predicate | anthemUsedIn |
P36220
|
FINISHED |
| Object | Puducherry |
—
|
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: Puducherry | Statement: [Tamil Thai, anthemUsedIn, Puducherry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anthemUsedIn Context triple: [Tamil Thai, anthemUsedIn, Puducherry]
-
A.
anthemType
Indicates the specific category or kind of anthem that characterizes the relationship between the subject and its anthem.
-
B.
anthemTitle
Indicates that the object is the title of the anthem associated with the subject.
-
C.
isAnthemFor
chosen
Indicates that a song or musical composition serves as the official anthem representing a particular group, organization, place, or cause.
-
D.
anthemOrRitual
Indicates a formal song or ceremonial practice that is officially associated with, or regularly performed by, a particular group, institution, or entity.
-
E.
anthemBackedBy
Indicates that an anthem is officially supported, endorsed, or accompanied by a particular backing entity, such as an organization, arrangement, or musical backing.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0560648190bb88db7255867d7f |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:19 p.m.