Triple
T267148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancashire and Yorkshire Railway |
E5755
|
entity |
| Predicate | servedIndustry |
P2193
|
FINISHED |
| Object | textile 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: textile industry | Statement: [Lancashire and Yorkshire Railway, servedIndustry, textile industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedIndustry Context triple: [Lancashire and Yorkshire Railway, servedIndustry, textile industry]
-
A.
sectorServed
chosen
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
B.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
C.
industryOfUnderlyingCompany
Indicates the industry sector in which the underlying company associated with this entity operates.
-
D.
sector
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
E.
hasHistoricIndustry
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25dacf60c8190a5c3ef455b9a8b20 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6f60b081908fc6467800a8849e |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.