Triple
T9764484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P.C. Hooftstraat |
E236750
|
entity |
| Predicate | streetCategory |
P44319
|
FINISHED |
| Object | luxury shopping street |
—
|
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: luxury shopping street | Statement: [P.C. Hooftstraat, streetCategory, luxury shopping street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetCategory Context triple: [P.C. Hooftstraat, streetCategory, luxury shopping street]
-
A.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
B.
streetOrAreaType
chosen
Indicates the specific kind or classification of a street or area (such as avenue, boulevard, district, or zone) associated with an entity.
-
C.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
-
D.
urbanSegmentName
Indicates the specific name assigned to a segment within an urban area or city layout.
-
E.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda09ed54c8190a5879e14184cddf4 |
completed | April 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.