Triple
T20551450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periya Puranam |
E504605
|
entity |
| Predicate | positionInTirumurai |
P140516
|
FINISHED |
| Object | twelfth Tirumurai |
—
|
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: twelfth Tirumurai | Statement: [Periya Puranam, positionInTirumurai, twelfth Tirumurai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTirumurai Context triple: [Periya Puranam, positionInTirumurai, twelfth Tirumurai]
-
A.
positionInDasamGranth
Indicates the specific location or ordering of a referenced element within the text of the Dasam Granth.
-
B.
positionInVeda
Indicates the specific location or ordering of a referenced element within the structure of a Vedic text.
-
C.
positionInJainTradition
Indicates the role, rank, or status an entity holds within the hierarchy or lineage of the Jain religious tradition.
-
D.
positionInMukhyaUpanishads
Indicates the specific ordinal placement or ranking that something occupies within the sequence of the principal (Mukhya) Upanishads.
-
E.
positionInGuruGranthSahib
Indicates the specific location or ordering of a referenced element within the text of the Guru Granth Sahib.
- F. None of above. chosen
Provenance (4 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5d8b55081909c3e3e972aff846d |
completed | April 20, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:38 a.m.