Triple
T29402052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shrimps |
E745669
|
entity |
| Predicate | reflectsIndustry |
P117301
|
FINISHED |
| Object | seafood industry of Morecambe |
—
|
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: seafood industry of Morecambe | Statement: [The Shrimps, reflectsIndustry, seafood industry of Morecambe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsIndustry Context triple: [The Shrimps, reflectsIndustry, seafood industry of Morecambe]
-
A.
reflectsBusiness
chosen
Indicates that one entity mirrors, represents, or corresponds to the business identity, operations, or interests of another entity.
-
B.
industryExposure
Indicates the extent to which an entity is involved in, affected by, or financially linked to a particular industry or set of industries.
-
C.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
D.
notableIndustry
Indicates that an entity is significantly recognized or prominent within a specified industry or sector.
-
E.
peakIndustry
Indicates that an entity is at the highest or most dominant level within a particular industry or sector.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 2:51 p.m.