Triple

T26182471
Position Surface form Disambiguated ID Type / Status
Subject M27 line E654722 entity
Predicate plannedInfrastructureType P56025 FINISHED
Object underground railway (likely) 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: underground railway (likely) | Statement: [M27 line, plannedInfrastructureType, underground railway (likely)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: plannedInfrastructureType
Context triple: [M27 line, plannedInfrastructureType, underground railway (likely)]
  • A. isPartOfInfrastructureType
    Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
  • B. builtInfrastructureType
    Indicates the specific kind or category of built infrastructure associated with or characterized by the subject.
  • C. proposedInfrastructure
    Indicates that an infrastructure project or facility has been suggested or planned but not yet approved, built, or implemented between the related entities.
  • D. typeOfTransportInfrastructure chosen
    Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
  • E. regionTypePlanned
    Indicates that a region is intended or designated to have a specific type or classification in a planned or future state.
  • 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_69ee5b469bc081908fe486453fdad810 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f6562fd3488190be1acd8c526a28d2 completed May 2, 2026, 7:53 p.m.
PD Predicate disambiguation batch_69f651a731508190bb0c8c2462eba224 completed May 2, 2026, 7:33 p.m.
Created at: April 26, 2026, 8:40 p.m.