Triple
T25283187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murugan bhakti movement |
E633869
|
entity |
| Predicate | usesLiterature |
P136618
|
FINISHED |
| Object | Tamil bhakti poetry |
—
|
LITERAL FINISHED |
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 bhakti poetry | Statement: [Murugan bhakti movement, usesLiterature, Tamil bhakti poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLiterature Context triple: [Murugan bhakti movement, usesLiterature, Tamil bhakti poetry]
-
A.
inLiterature
Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
-
B.
literaryInterest
Indicates that one entity has an interest in, appreciation of, or engagement with the literary works or writings of another entity.
-
C.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
D.
literaryUse
chosen
Indicates that something is employed or referenced within a literary context, such as in a written work, style, or technique.
-
E.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0718908190a2ebc862db79e2ea |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:19 p.m.