Triple
T4701068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruinisse |
E104270
|
entity |
| Predicate | hasWaterBasedRecreation |
P8966
|
FINISHED |
| Object | marina |
—
|
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: marina | Statement: [Bruinisse, hasWaterBasedRecreation, marina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterBasedRecreation Context triple: [Bruinisse, hasWaterBasedRecreation, marina]
-
A.
hasWaterActivity
Indicates that one entity possesses, exhibits, or is characterized by a particular level or type of water-related activity (such as moisture content, water availability, or water-based processes).
-
B.
hasBoatRamp
Indicates that a location provides a designated ramp or launch area for putting boats into the water or taking them out.
-
C.
recreationAccess
chosen
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
D.
hasWaterfrontPark
Indicates that a place or area includes or is associated with a park located directly along a body of water.
-
E.
hasWaterPark
Indicates that one entity possesses, includes, or features a water park as part of its facilities or attributes.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.