Triple
T13307017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Kom Ombo |
E316959
|
entity |
| Predicate | constructionStartedInPeriod |
P53662
|
FINISHED |
| Object | Ptolemaic period |
—
|
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: Ptolemaic period | Statement: [Temple of Kom Ombo, constructionStartedInPeriod, Ptolemaic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionStartedInPeriod Context triple: [Temple of Kom Ombo, constructionStartedInPeriod, Ptolemaic period]
-
A.
constructionStartYear
Indicates the calendar year in which the construction of something was begun.
-
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.
constructionStartAfter
Indicates that the start of one construction activity or project occurs after the start of another specified construction activity or project.
-
D.
hasBuildingPeriod
chosen
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
E.
buildingConstructionStart
Indicates the point in time when the construction work on a building begins.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.