Triple
T28578124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oude Kerk |
E723297
|
entity |
| Predicate | isLocatedInRedLightDistrict |
P120961
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oude Kerk, isLocatedInRedLightDistrict, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInRedLightDistrict Context triple: [Oude Kerk, isLocatedInRedLightDistrict, true]
-
A.
isEntertainmentDistrict
Indicates that a location functions primarily as an area dedicated to entertainment activities, venues, and nightlife.
-
B.
isLocatedInCityWithClub
Indicates that an entity is situated in a city that has at least one (sports or similar) club based there.
-
C.
isLocatedInHistoricSquare
Indicates that an entity is situated within a square that is recognized as historically significant.
-
D.
isLocatedInDistrictKnownFor
chosen
Indicates that an entity is situated within a district that is notably recognized for a particular characteristic, feature, or reputation.
-
E.
hasStreetLifeCharacteristic
Indicates that an entity exhibits a particular quality, feature, or condition related to street life or street-level activity.
- 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_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 4:13 a.m.