Triple
T14031926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester canal network |
E337610
|
entity |
| Predicate | supportedIndustry |
P112563
|
FINISHED |
| Object | cotton 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: cotton industry | Statement: [Manchester canal network, supportedIndustry, cotton industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedIndustry Context triple: [Manchester canal network, supportedIndustry, cotton industry]
-
A.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
B.
sponsorshipIndustry
Indicates a relationship where one entity sponsors another specifically within a given industry or sector context.
-
C.
sponsorIndustry
Indicates that an entity acts as a sponsor for, or is financially or organizationally supporting, a particular industry or industrial sector.
-
D.
industryStart
Indicates the point in time or event at which an industry, industrial activity, or industrial era begins.
-
E.
foundingIndustry
Indicates the industry or sector in which an entity was originally founded or began its primary operations.
- F. None of above. chosen
Provenance (4 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fab17008190981f1808726fa11c |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:20 p.m.