Triple
T11122140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kannada literature |
E263040
|
entity |
| Predicate | earliestEvidenceCentury |
P11826
|
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: [Kannada literature, earliestEvidenceCentury, 9th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestEvidenceCentury Context triple: [Kannada literature, earliestEvidenceCentury, 9th century]
-
A.
earliestCultEvidence
Indicates the earliest known archaeological or historical evidence for the existence of a particular cult or organized worship practice.
-
B.
earliestEvidenceSite
Indicates that the related site is the location where the earliest known evidence of the subject was found.
-
C.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
-
D.
attestedFromCentury
chosen
Indicates the century from which there is evidence or documentation that something is known to exist or be in use.
-
E.
affirmedInCentury
Indicates that a statement, belief, or status was formally confirmed or upheld during a specified century.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79afa0ab88190ab6d61df8cf485ec |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.