Triple
T15395635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Dutch Church |
E368169
|
entity |
| Predicate | hasPredecessorBuildingsFrom |
P85130
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Old Dutch Church, hasPredecessorBuildingsFrom, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredecessorBuildingsFrom Context triple: [Old Dutch Church, hasPredecessorBuildingsFrom, 17th century]
-
A.
hasFormerBuilding
Indicates that an entity previously occupied or used a different building, which is identified as its former building.
-
B.
predecessorBuildingDate
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
C.
hasBuildingFrom
chosen
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
D.
hasOriginalBuildings
Indicates that an entity possesses or still retains its initial or historically first-constructed buildings.
-
E.
laterBuiltOverBy
Indicates that a structure or feature was constructed at a later time on top of, or replacing, an earlier one.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8ac79081908ac79c0b3e7587ff |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.