Triple

T12489316
Position Surface form Disambiguated ID Type / Status
Subject Charing Cross, Euston and Hampstead Railway E298519 entity
Predicate usedPowerSupply P44389 FINISHED
Object electric third-rail system 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: electric third-rail system | Statement: [Charing Cross, Euston and Hampstead Railway, usedPowerSupply, electric third-rail system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedPowerSupply
Context triple: [Charing Cross, Euston and Hampstead Railway, usedPowerSupply, electric third-rail system]
  • A. hasPowerSupplyType chosen
    Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
  • B. powerSupplyCapability
    Indicates the ability of one entity to provide electrical power to another entity or system.
  • C. powerSupplyLocation
    Indicates the physical place or component where an entity’s electrical power is provided or connected.
  • D. powerAdapter
    Indicates that one entity serves as a power adapter, converting or supplying electrical power for another entity.
  • E. hasPowerRegulator
    Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
  • 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_69d6ada377208190a36011199a4d8558 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94e8a706c8190873623eab7db607d completed April 10, 2026, 7:24 p.m.
PD Predicate disambiguation batch_69d94d41f3cc8190a3331fb9a895306f completed April 10, 2026, 7:19 p.m.
Created at: April 8, 2026, 9:56 p.m.