Triple
T878744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oude Kerk, Delft |
E18978
|
entity |
| Predicate | leaningDirection |
P15748
|
FINISHED |
| Object | slightly westward |
—
|
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: slightly westward | Statement: [Oude Kerk, Delft, leaningDirection, slightly westward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaningDirection Context triple: [Oude Kerk, Delft, leaningDirection, slightly westward]
-
A.
offsetDirection
chosen
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
B.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
C.
orientation
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
D.
frontLineDirection
Indicates the primary orientation or bearing in which the front line of a conflict, formation, or boundary is facing or advancing.
-
E.
declination
Indicates the angular deviation of one direction or object from a reference plane or axis, typically measuring how far it is tilted or offset.
- 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_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. |
Created at: March 1, 2026, 7:39 p.m.