Triple
T15991009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Luzia (Tavira) |
E387822
|
entity |
| Predicate | primarySeafoodSpecialty |
P79990
|
FINISHED |
| Object | octopus dishes |
—
|
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: octopus dishes | Statement: [Santa Luzia (Tavira), primarySeafoodSpecialty, octopus dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySeafoodSpecialty Context triple: [Santa Luzia (Tavira), primarySeafoodSpecialty, octopus dishes]
-
A.
seafoodSpecialty
chosen
Indicates that one entity specializes in preparing, serving, or producing seafood as a primary focus or notable expertise.
-
B.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
C.
majorFisheryRegion
Indicates that a location is recognized as a primary or significant region for fishing activities or fishery production.
-
D.
fisheriesProduct
Indicates that something is a product derived from fishing activities or the harvesting of aquatic organisms.
-
E.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4e871c819082d7b1c1eaf5b4fe |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.