Triple
T24147754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yerseke |
E598432
|
entity |
| Predicate | hasSeafoodProduct |
P79990
|
FINISHED |
| Object | Zeeland mussels |
—
|
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: Zeeland mussels | Statement: [Yerseke, hasSeafoodProduct, Zeeland mussels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeafoodProduct Context triple: [Yerseke, hasSeafoodProduct, Zeeland mussels]
-
A.
containsFish
Indicates that one entity holds, includes, or has fish within its boundaries or contents.
-
B.
seafoodSpecialty
chosen
Indicates that one entity specializes in preparing, serving, or producing seafood as a primary focus or notable expertise.
-
C.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
D.
containsOffal
Indicates that something includes or is made with animal offal (internal organs or entrails) as part of its contents.
-
E.
includesSea
Indicates that one geographic or administrative area contains or encompasses a sea within its boundaries or extent.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00c42288190843962f9476a94a1 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:30 p.m.