Triple

T30985339
Position Surface form Disambiguated ID Type / Status
Subject Thames and Medway Canal E789508 entity
Predicate railwayConversionDate P180161 FINISHED
Object 1840s 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: 1840s | Statement: [Thames and Medway Canal, railwayConversionDate, 1840s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayConversionDate
Context triple: [Thames and Medway Canal, railwayConversionDate, 1840s]
  • A. railwaySectionOpeningDate
    Indicates the date on which a specific section of a railway line was officially opened for operation.
  • B. dateOfConversion
    Indicates the specific date on which an entity changed status, form, or affiliation (e.g., religious, legal, or organizational conversion).
  • C. railwayOpenedWith
    Indicates that a railway line or section was inaugurated and began operation together with a specified associated element (such as a station, segment, or service).
  • D. railwayOpeningPeriod
    Indicates the time span during which a railway line or station was officially opened and in operation.
  • E. railwayWorksOpened
    Indicates that a railway facility, such as a station, line, or related infrastructure, was officially opened or began operation on a specified date.
  • 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_69f224c550b081909ddfceb0c3d03bdd completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f73223675481908c1bc3208c0f5284 completed May 3, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69f7317690108190b3aae2cd2e1d069e completed May 3, 2026, 11:28 a.m.
PDg Predicate description generation batch_69f73221eef88190bd8905e6e9f5a586 completed May 3, 2026, 11:31 a.m.
Created at: April 29, 2026, 8:56 p.m.