Triple
T25692941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periyalvar |
E644245
|
entity |
| Predicate | numberOfVersesAttributed |
P89516
|
FINISHED |
| Object | about 473 |
—
|
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: about 473 | Statement: [Periyalvar, numberOfVersesAttributed, about 473]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfVersesAttributed Context triple: [Periyalvar, numberOfVersesAttributed, about 473]
-
A.
hasVerseCount
Indicates that an entity (such as a text or section) is associated with a specific number of verses it contains.
-
B.
numberOfAttributedHymns
chosen
Indicates the quantity of hymns that are credited or assigned to a particular entity as their author or source.
-
C.
approximateNumberOfVerses
Indicates an estimated or approximate count of verses associated with an entity.
-
D.
hasVersesBy
Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
-
E.
hasVersesIn
Indicates that one entity (typically a text, chapter, or section) contains or is composed of verses found within another entity (such as a book, collection, or scripture).
- 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_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 21, 2026, 8:30 p.m.