Triple
T4522599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Church (Delft) |
E103302
|
entity |
| Predicate | towerConstructionStart |
P14638
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [Old Church (Delft), towerConstructionStart, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerConstructionStart Context triple: [Old Church (Delft), towerConstructionStart, 14th century]
-
A.
buildingConstructionStart
chosen
Indicates the point in time when the construction work on a building begins.
-
B.
startConstruction
Indicates that an entity initiates the process of building or constructing another entity or structure.
-
C.
towerCompleted
Indicates that the construction of a tower has been fully finished and reached its intended completed state.
-
D.
towerCompletedBefore
Indicates that the construction or completion of one tower occurred earlier in time than the construction or completion of another tower.
-
E.
constructionStartAfter
Indicates that the start of one construction activity or project occurs after the start of another specified construction activity or project.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd574bd6908190b939d92b5809b101 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.