Triple
T29014001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grote Kerk (Dordrecht) |
E737248
|
entity |
| Predicate | towerClimbPossible |
P97394
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Grote Kerk (Dordrecht), towerClimbPossible, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerClimbPossible Context triple: [Grote Kerk (Dordrecht), towerClimbPossible, yes]
-
A.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
B.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within another entity.
-
C.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
D.
towerAccessibleTo
Indicates that a particular tower can be reached, entered, or used by a specified agent or group under given conditions.
-
E.
climbingAllowed
chosen
Indicates that an entity is permitted to climb onto or up another entity or surface.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fdfb82c81908eda8bded5074241 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:44 a.m.