Triple
T20552020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tevaram hymns |
E504617
|
entity |
| Predicate | latestCompositionCentury |
P41949
|
FINISHED |
| Object | 9th 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: 9th century | Statement: [Tevaram hymns, latestCompositionCentury, 9th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestCompositionCentury Context triple: [Tevaram hymns, latestCompositionCentury, 9th century]
-
A.
probableCenturyOfComposition
chosen
Indicates the century in which something (typically a work or composition) was most likely created or written.
-
B.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
C.
historicalComposition
Indicates that one entity was historically part of, or contributed to the makeup or structure of, another entity during a past period.
-
D.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
E.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
- 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.