Triple
T46118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North West England |
E903
|
entity |
| Predicate | hasIndustrialHeritage |
P2411
|
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: [North West England, hasIndustrialHeritage, textile industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustrialHeritage Context triple: [North West England, hasIndustrialHeritage, textile industry]
-
A.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
B.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
C.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
D.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
E.
hasHeritageDesignation
Indicates that an entity has been formally assigned a specific heritage or cultural protection status by an authoritative body.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24b1bf2c081908f20e13939b713ff |
completed | Feb. 28, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69a24abd07508190a83ffba5368c1c79 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24b1a42888190b56a5e457e11604f |
completed | Feb. 28, 2026, 1:55 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.