Triple
T456666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian script |
E7247
|
entity |
| Predicate | timeOfEmergence |
P2559
|
FINISHED |
| Object | early 1st millennium CE |
—
|
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: early 1st millennium CE | Statement: [Georgian script, timeOfEmergence, early 1st millennium CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfEmergence Context triple: [Georgian script, timeOfEmergence, early 1st millennium CE]
-
A.
emergedAround
chosen
Indicates that something came into existence or became noticeable at approximately a particular time or period.
-
B.
extinctionPeriod
Indicates the time span during which an entity ceases to exist or is considered extinct.
-
C.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
-
D.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
E.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another entity.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa1616481909399f92551a0c9e3 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.