Triple
T20656505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames and Severn Canal (disused) near Radcot |
E507638
|
entity |
| Predicate | engineeringPeriod |
P140944
|
FINISHED |
| Object | British industrial era |
—
|
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: British industrial era | Statement: [Thames and Severn Canal (disused) near Radcot, engineeringPeriod, British industrial era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringPeriod Context triple: [Thames and Severn Canal (disused) near Radcot, engineeringPeriod, British industrial era]
-
A.
designPeriod
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
B.
engineeringEmphasis
Indicates that something places a primary focus or specialization on engineering principles, methods, or activities.
-
C.
timePeriodOfProduction
Indicates the span of time during which something was produced or created.
-
D.
hasDesignPeriod
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
E.
engineSupplierPeriod
Indicates the time period during which an entity serves as the engine supplier for another entity.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2ed48308190b9350a323b9a7952 |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.