Triple
T12817373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euromos |
E306435
|
entity |
| Predicate | approximateDateOfTempleConstruction |
P13262
|
FINISHED |
| Object | 2nd 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: 2nd century CE | Statement: [Euromos, approximateDateOfTempleConstruction, 2nd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfTempleConstruction Context triple: [Euromos, approximateDateOfTempleConstruction, 2nd century CE]
-
A.
plannedTempleDedicatedBy
Indicates that a temple, while still in the planning or unbuilt stage, is intended or designated to be dedicated by a specific agent or entity.
-
B.
estimatedYearOfCreation
chosen
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
C.
datePlannedTempleCornerstonesLaid
Indicates the planned date on which the temple’s cornerstones are scheduled to be laid.
-
D.
foundedAsTempleInYear
Indicates that an entity was originally established as a temple in a specific year.
-
E.
templeConstruction
Indicates the action or process of building, erecting, or establishing a temple or similar sacred structure.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9d00088190ac0f5d60e1de7a7c |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.