Triple
T20552019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tevaram hymns |
E504617
|
entity |
| Predicate | earliestCompositionCentury |
P41949
|
FINISHED |
| Object | 7th century |
—
|
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: 7th century | Statement: [Tevaram hymns, earliestCompositionCentury, 7th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestCompositionCentury Context triple: [Tevaram hymns, earliestCompositionCentury, 7th century]
-
A.
probableCenturyOfComposition
chosen
Indicates the century in which something (typically a work or composition) was most likely created or written.
-
B.
firstPerformedCentury
Indicates the century in which an action, work, or performance was first carried out or presented.
-
C.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
D.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
earliestCompilationAttributedTo
Indicates that one entity is regarded as the earliest known or first compilation associated with, or attributed to, 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5d98c348190ac516bc2df59d878 |
completed | April 20, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.