Triple
T911965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Crypt in Nieuwe Kerk, Delft |
E19678
|
entity |
| Predicate | locatedBelow |
P10157
|
FINISHED |
| Object | nave of the Nieuwe Kerk, Delft |
—
|
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: nave of the Nieuwe Kerk, Delft | Statement: [Royal Crypt in Nieuwe Kerk, Delft, locatedBelow, nave of the Nieuwe Kerk, Delft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedBelow Context triple: [Royal Crypt in Nieuwe Kerk, Delft, locatedBelow, nave of the Nieuwe Kerk, Delft]
-
A.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
-
B.
locatedUnder
chosen
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
C.
locatedAtBaseOf
Indicates that one entity is positioned at or near the bottom or lowest supporting part of another entity.
-
D.
clearanceBelow
Indicates that one entity is positioned at a lower vertical clearance level than another, typically with less space between it and an underlying reference surface.
-
E.
locatedSouthOf
Indicates that one entity is positioned geographically to the south of another entity.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2f605bc8190a5245aa2ca55cf43 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b2918ea881908698020b995a8eae |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.