Triple

T34174680
Position Surface form Disambiguated ID Type / Status
Subject Hamburg U-Bahn line U3 E876632 entity
Predicate runsAboveGround P135994 FINISHED
Object largely 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: largely | Statement: [Hamburg U-Bahn line U3, runsAboveGround, largely]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: runsAboveGround
Context triple: [Hamburg U-Bahn line U3, runsAboveGround, largely]
  • A. locatedAboveGround chosen
    Indicates that one entity is positioned at a level higher than the ground surface, not buried or below ground.
  • B. heightAboveGround
    Indicates the vertical distance of an entity measured from the ground surface directly beneath it.
  • C. usesGroundFor
    Indicates that one entity makes functional or practical use of a particular ground, surface, or land area for its activities or purposes.
  • D. runsBeneath
    Indicates that one entity extends or moves below another entity along its length or span.
  • E. hasFloorsAboveGround
    Indicates that an entity (typically a building or structure) possesses a specified number of floors that are located above ground level.
  • 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_69f349ad97ac8190bf1f17417c970e64 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70fe897048190971b6dc1f9e29f85 completed May 3, 2026, 9:05 a.m.
PD Predicate disambiguation batch_69f70f3c5bfc81908585f52e196dafe5 completed May 3, 2026, 9:02 a.m.
Created at: May 1, 2026, 1:54 a.m.