Triple
T7780534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paulus Potterstraat |
E221502
|
entity |
| Predicate | hasAttractionTypeNearby |
P8648
|
FINISHED |
| Object | artMuseum |
—
|
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: artMuseum | Statement: [Paulus Potterstraat, hasAttractionTypeNearby, artMuseum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttractionTypeNearby Context triple: [Paulus Potterstraat, hasAttractionTypeNearby, artMuseum]
-
A.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
B.
hasAttractionType
chosen
Indicates that one entity is associated with a specific kind or category of attraction (e.g., tourist, cultural, natural).
-
C.
isAttractionFor
Indicates that one entity serves as an attraction or point of interest specifically intended for another entity (such as a person, group, or audience).
-
D.
containsAttraction
Indicates that one entity includes or encompasses an attraction (such as a point of interest, feature, or draw) within its bounds or scope.
-
E.
nearbyVenue
Indicates that one venue is located close to another venue in physical space.
- 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:20 p.m.