Triple
T23004553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jetavanaramaya |
E572726
|
entity |
| Predicate | constructionCompletionApproximateDate |
P62932
|
FINISHED |
| Object | 4th century 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: 4th century CE | Statement: [Jetavanaramaya, constructionCompletionApproximateDate, 4th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionCompletionApproximateDate Context triple: [Jetavanaramaya, constructionCompletionApproximateDate, 4th century CE]
-
A.
laterDamCompletionDate
Indicates that one dam’s completion date occurs chronologically after another dam’s completion date.
-
B.
startOfConstructionApprox
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
-
C.
claimedConstructionDate
Indicates the date on which an entity is asserted or reported to have been constructed, according to some claim or source.
-
D.
archCompletionDate
chosen
Indicates the date on which an architectural element, project, or structure was completed.
-
E.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183556cd08190b18780680bc4f23e |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.