Triple
T21586785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Greymouth |
E532670
|
entity |
| Predicate | currentPrimaryIndustryServed |
P2193
|
FINISHED |
| Object | fishing industry |
—
|
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: fishing industry | Statement: [Port of Greymouth, currentPrimaryIndustryServed, fishing industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPrimaryIndustryServed Context triple: [Port of Greymouth, currentPrimaryIndustryServed, fishing industry]
-
A.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
B.
sectorServed
chosen
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
C.
supportedIndustry
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
-
D.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
E.
strategicAreaServed
Indicates that an entity provides services or exerts influence within a particular area considered strategically important.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb6137fc8190840b7c1275e62a1d |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.