Triple
T9013971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aasee (Münster) |
E215546
|
entity |
| Predicate | shoreHas |
P85723
|
FINISHED |
| Object | event venues |
—
|
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: event venues | Statement: [Aasee (Münster), shoreHas, event venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoreHas Context triple: [Aasee (Münster), shoreHas, event venues]
-
A.
shore
Indicates a relationship where one entity forms or lies along the edge or boundary of a body of water, such as a sea, lake, or river.
-
B.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
C.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
D.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
E.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
- F. None of above. chosen
Provenance (4 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69fae0b88190a0aa989bc37ab2c7 |
completed | April 1, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:06 p.m.