Triple
T1846862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asomtavruli |
E41302
|
entity |
| Predicate | earliestAttestationCentury |
P11826
|
FINISHED |
| Object | 5th 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: 5th century | Statement: [Asomtavruli, earliestAttestationCentury, 5th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestAttestationCentury Context triple: [Asomtavruli, earliestAttestationCentury, 5th century]
-
A.
attestedFromCentury
chosen
Indicates the century from which there is evidence or documentation that something is known to exist or be in use.
-
B.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
-
C.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
D.
approximateStartCentury
Indicates the century in which something is estimated or roughly believed to have begun.
-
E.
firstClearlyAttestedIn
Indicates the earliest known point in time or source where something is clearly documented or evidenced.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.