Triple
T43502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Dendur |
E855
|
entity |
| Predicate | installationCompleted |
P3055
|
FINISHED |
| Object | 1978 |
—
|
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: 1978 | Statement: [Temple of Dendur, installationCompleted, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installationCompleted Context triple: [Temple of Dendur, installationCompleted, 1978]
-
A.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
domeCompleted
Indicates that the construction or formation of a dome structure has been fully finished.
-
D.
renovationCompleted
Indicates that a renovation process for an entity has been fully finished and is no longer in progress.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
- F. None of above. chosen
Provenance (4 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24c083ad081909c1122c8fb29efdc |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24aba9a2c81909f769a8f22e30c92 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24c0794c0819095509d970e05fc0f |
completed | Feb. 28, 2026, 1:59 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.