Triple
T5902915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Pijp |
E131269
|
entity |
| Predicate | AlbertCuypMarketType |
P2821
|
FINISHED |
| Object | daily street market |
—
|
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: daily street market | Statement: [De Pijp, AlbertCuypMarketType, daily street market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AlbertCuypMarketType Context triple: [De Pijp, AlbertCuypMarketType, daily street market]
-
A.
streetType_MarketStreet
Indicates that the street’s type or classification is specifically designated as “Market Street.”
-
B.
hasShoppingDistrictName
Indicates that an entity’s shopping district is identified by a specific name.
-
C.
gatheringPlace
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
D.
marketType
chosen
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
-
E.
hasShoppingDistrict
Indicates that a place contains or is associated with a designated area where multiple shops and commercial retail activities are concentrated.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.