Triple
T5720615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zandvoort |
E126133
|
entity |
| Predicate | hasBeachResort |
P1922
|
FINISHED |
| Object | Zandvoort aan Zee |
—
|
NE NERFINISHED |
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: Zandvoort aan Zee | Statement: [Zandvoort, hasBeachResort, Zandvoort aan Zee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeachResort Context triple: [Zandvoort, hasBeachResort, Zandvoort aan Zee]
-
A.
hasBeach
chosen
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
B.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
C.
hasBeachTagRequirement
Indicates that something is subject to a specific requirement or condition related to beach access, use, or tagging.
-
D.
isSeasideResort
Indicates that a place functions as a resort located by the sea, typically offering coastal leisure and tourism activities.
-
E.
hasSpaResort
Indicates that one entity possesses, includes, or is associated with a spa resort as an amenity or feature.
- 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_69c0082e3d548190950169847b43043b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c47f4c81909e6849c3be3e951c |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.