Triple
T25693073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pey Alvar |
E644248
|
entity |
| Predicate | collectiveWork |
P136157
|
FINISHED |
| Object | Divya Prabandham |
—
|
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: Divya Prabandham | Statement: [Pey Alvar, collectiveWork, Divya Prabandham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveWork Context triple: [Pey Alvar, collectiveWork, Divya Prabandham]
-
A.
collaborativeWork
Indicates a relationship where two or more entities jointly contribute effort or resources toward a shared task, project, or goal.
-
B.
workCollectedBy
chosen
Indicates that a created work has been gathered, acquired, or included within a collection maintained by another entity.
-
C.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
D.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
E.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 8:30 p.m.