Triple
T20157112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferryland |
E491598
|
entity |
| Predicate | hasIndustryHistorical |
P3008
|
FINISHED |
| Object | cod fishery |
—
|
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: cod fishery | Statement: [Ferryland, hasIndustryHistorical, cod fishery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustryHistorical Context triple: [Ferryland, hasIndustryHistorical, cod fishery]
-
A.
hasHistoricIndustry
chosen
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
B.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
-
C.
hasHistoricMarket
Indicates that an entity possesses or is the location of a market of historical significance.
-
D.
hadStateOwnershipOfIndustry
Indicates that a governing authority or state entity possessed ownership and control over a particular industry.
-
E.
hasHistoricalCategory
Indicates that something is associated with a particular historical classification, period, or type based on its past context or significance.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e18a0c8190a2cc2b305da28047 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:34 p.m.