Triple
T28578180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethlehemsteeg |
E723299
|
entity |
| Predicate | hasPassagewayWidth |
P60150
|
FINISHED |
| Object | narrow |
—
|
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: narrow | Statement: [Bethlehemsteeg, hasPassagewayWidth, narrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassagewayWidth Context triple: [Bethlehemsteeg, hasPassagewayWidth, narrow]
-
A.
hasWalkwayWidth
Indicates the width measurement of a walkway in the relationship between a walkway and its specified dimension.
-
B.
hasNarrowEntrance
Indicates that an entity possesses an entrance that is relatively small or restricted in width compared to typical or surrounding access points.
-
C.
hasEntrancePassageLength
Indicates the length of an entrance passage associated with an entity.
-
D.
entranceWidth
chosen
Indicates the measured horizontal span of an entrance opening that defines how wide the entry passage is.
-
E.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 28, 2026, 4:13 a.m.