Triple
T7107256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple I |
E165618
|
entity |
| Predicate | constructionEndTime |
P52553
|
FINISHED |
| Object | 8th century |
—
|
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: 8th century | Statement: [Temple I, constructionEndTime, 8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionEndTime Context triple: [Temple I, constructionEndTime, 8th century]
-
A.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
-
B.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
C.
constructionCompletedUnder
Indicates that the completion of a construction project occurred under the responsibility, authority, or supervision of a specified agent, organization, or governing body.
-
D.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
E.
buildPeriodEnd
chosen
Indicates the point in time at which a construction or building phase is considered 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b9f13c8190a14898f241ec17a4 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.