Triple
T878745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oude Kerk, Delft |
E18978
|
entity |
| Predicate | hasNave |
P21022
|
FINISHED |
| Object | three-aisled nave |
—
|
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: three-aisled nave | Statement: [Oude Kerk, Delft, hasNave, three-aisled nave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNave Context triple: [Oude Kerk, Delft, hasNave, three-aisled nave]
-
A.
naveHeight
Indicates the vertical distance from the floor to the highest point of the nave space in a building.
-
B.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
C.
naveLength
Indicates the length measurement of a building’s nave, typically from the entrance to the chancel or crossing.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acb1dc20819095b9bb093158b60d |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:39 p.m.