Triple
T725298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dravidian languages |
E14711
|
entity |
| Predicate | oldestInscriptionsDate |
P3921
|
FINISHED |
| Object | at least 3rd century BCE |
—
|
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: at least 3rd century BCE | Statement: [Dravidian languages, oldestInscriptionsDate, at least 3rd century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oldestInscriptionsDate Context triple: [Dravidian languages, oldestInscriptionsDate, at least 3rd century BCE]
-
A.
inscribedOn
Indicates that text, symbols, or markings are written or carved onto the surface of an object.
-
B.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
C.
numberOfInscriptions
Indicates the total count of inscriptions associated with a given entity or object.
-
D.
firstClearlyAttestedIn
chosen
Indicates the earliest known point in time or source where something is clearly documented or evidenced.
-
E.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5a7fb7c819096db848fe2ba246a |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f700cc81908c6de3eedf68433c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.