Triple
T23004552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jetavanaramaya |
E572726
|
entity |
| Predicate | constructionStartApproximateDate |
P106367
|
FINISHED |
| Object | 3rd 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: 3rd century CE | Statement: [Jetavanaramaya, constructionStartApproximateDate, 3rd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionStartApproximateDate Context triple: [Jetavanaramaya, constructionStartApproximateDate, 3rd century CE]
-
A.
startOfConstructionApprox
chosen
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
-
B.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
C.
constructionStartYear
Indicates the calendar year in which the construction of something was begun.
-
D.
constructionStartAfter
Indicates that the start of one construction activity or project occurs after the start of another specified construction activity or project.
-
E.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
- 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.