Triple

T24102881
Position Surface form Disambiguated ID Type / Status
Subject Newport Bridge (Middlesbrough) E597134 entity
Predicate hasLiftFunction P35396 FINISHED
Object originally yes 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: originally yes | Statement: [Newport Bridge (Middlesbrough), hasLiftFunction, originally yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLiftFunction
Context triple: [Newport Bridge (Middlesbrough), hasLiftFunction, originally yes]
  • A. hasLift chosen
    Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
  • B. hasLiftType
    Indicates the specific type or category of lift associated with an entity.
  • C. hasLFunction
    Indicates that an entity possesses or is associated with a specific L-function, typically representing a complex analytic function linked to its arithmetic or geometric properties.
  • D. hasUpperLevelFunction
    Indicates that one function operates at a higher or more abstract level than another function within a hierarchical relationship.
  • E. hasHighestLift
    Indicates that the subject entity achieves the greatest lift value (e.g., improvement or elevation relative to a baseline) compared to all other relevant entities in the given context.
  • 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_69e288c60f9c8190af948d7354aedbeb completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1dd2ad01881909aa5a3c300009086 completed April 29, 2026, 10:27 a.m.
PD Predicate disambiguation batch_69f17651458c8190bbfd301883e46085 completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 11 p.m.