Triple
T629793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Widnes |
E15899
|
entity |
| Predicate | industrialDevelopmentBegan |
P10779
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Widnes, industrialDevelopmentBegan, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialDevelopmentBegan Context triple: [Widnes, industrialDevelopmentBegan, 19th century]
-
A.
historicalPeakIndustrialPeriod
Indicates the time period during which an entity reached its highest level of industrial activity or development.
-
B.
developmentBegan
chosen
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
isIndustrialCenter
Indicates that a place functions as a major hub of industrial activity, production, or manufacturing within a region.
-
D.
estimatedIndustrialScale
Indicates that an entity has been assessed or projected to operate at an industrial (large-scale) level of production or activity.
-
E.
hasIndustrialHeritage
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec051bc8190b3e3f8651a367d77 |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d01b29081908be87e4cd7726ff1 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.