Triple
T20181917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torfaen valley |
E492748
|
entity |
| Predicate | industrialPeriod |
P34306
|
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: [Torfaen valley, industrialPeriod, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialPeriod Context triple: [Torfaen valley, industrialPeriod, 19th century]
-
A.
timePeriodOfIndustrialization
chosen
Indicates the time period during which a given entity underwent industrialization.
-
B.
historicalPeakIndustrialPeriod
Indicates the time period during which an entity reached its highest level of industrial activity or development.
-
C.
modernIndustry
Indicates that an entity operates within or is characteristic of contemporary, technologically advanced industrial practices and sectors.
-
D.
modernizationPeriod
Indicates the time span during which an entity undergoes or is subject to modernization efforts or processes.
-
E.
historicalPeriodOfRapidDevelopment
Indicates a time span during which something undergoes unusually fast or intense growth, change, or advancement compared to other periods.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ef9370819091a8479f811002a9 |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.