Triple
T19843997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duladeo Temple |
E476809
|
entity |
| Predicate | estimatedCompletionCentury |
P83221
|
FINISHED |
| Object | 12th 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: 12th century | Statement: [Duladeo Temple, estimatedCompletionCentury, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedCompletionCentury Context triple: [Duladeo Temple, estimatedCompletionCentury, 12th century]
-
A.
estimatedConstructionEndCentury
chosen
Indicates the century in which the construction of something is estimated to have been completed.
-
B.
completedInCentury
Indicates that an action, event, or creation was finished during a specified century.
-
C.
approximateActivityEndCentury
Indicates the century in which an activity or action is estimated to have ended, based on approximate or uncertain dating.
-
D.
approximateCompletionEra
Indicates the general historical period or time range during which something was completed, without specifying an exact date.
-
E.
approximateUseEndCentury
Indicates that something’s period of use ended around, but not necessarily exactly in, a specified century.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658085a148190a305bde0897dfe84 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.