Triple
T25161730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeongdeok County |
E626455
|
entity |
| Predicate | hasSeafoodResource |
P11760
|
FINISHED |
| Object | snow crab |
—
|
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: snow crab | Statement: [Yeongdeok County, hasSeafoodResource, snow crab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeafoodResource Context triple: [Yeongdeok County, hasSeafoodResource, snow crab]
-
A.
hasMarineResource
chosen
Indicates that one entity possesses, contains, or is associated with a marine (ocean or sea-based) resource in relation to another entity.
-
B.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
containsFish
Indicates that one entity holds, includes, or has fish within its boundaries or contents.
-
D.
seafoodSpecialty
Indicates that one entity specializes in preparing, serving, or producing seafood as a primary focus or notable expertise.
-
E.
hasMarineSpecies
Indicates that an entity contains, supports, or is associated with one or more marine species.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 18, 2026, 6:31 a.m.