Triple
T246889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telugu |
E5056
|
entity |
| Predicate | earliestKnownInscriptionCentury |
P3921
|
FINISHED |
| Object | 6th 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: 6th century | Statement: [Telugu, earliestKnownInscriptionCentury, 6th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestKnownInscriptionCentury Context triple: [Telugu, earliestKnownInscriptionCentury, 6th century]
-
A.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
B.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
-
C.
firstClearlyAttestedIn
chosen
Indicates the earliest known point in time or source where something is clearly documented or evidenced.
-
D.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
E.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d13b8088190a3f48f0388d57496 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.