Triple

T23898794
Position Surface form Disambiguated ID Type / Status
Subject Central line – Piccadilly line E600980 entity
Predicate isKeyConnectionPoint P97647 FINISHED
Object true 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: true | Statement: [Central line – Piccadilly line, isKeyConnectionPoint, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isKeyConnectionPoint
Context triple: [Central line – Piccadilly line, isKeyConnectionPoint, true]
  • A. isKeyConnectionPointFor chosen
    Indicates that something serves as a primary or critical linking point that connects or integrates other elements within a system or structure.
  • B. hasKeyPoint
    Indicates that one entity includes, contains, or is associated with a specific key point or main idea represented by another entity.
  • C. isKeyEndpointOf
    Indicates that one endpoint in a connection, link, or structure serves as the primary or designated key endpoint of the other.
  • D. isKeyPostIn
    Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
  • E. isReferencePointFor
    Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
  • 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_69e295341ac0819080647f2908af793c completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1cddca9708190acd3e9edc9b5940b completed April 29, 2026, 9:22 a.m.
PD Predicate disambiguation batch_69f1614e24b48190a1c8fb5b7c75ee0f completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:25 p.m.