Triple

T4385245
Position Surface form Disambiguated ID Type / Status
Subject UP Express E99224 entity
Predicate offersOnboardPowerOutlets P56287 FINISHED
Object 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: yes | Statement: [UP Express, offersOnboardPowerOutlets, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offersOnboardPowerOutlets
Context triple: [UP Express, offersOnboardPowerOutlets, yes]
  • A. hasPowerRegulator
    Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
  • B. suppliesPowerTo
    Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
  • C. hasPowerSupplyType
    Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
  • D. usesElectricalPlug
    Indicates that one entity operates by being connected to another entity via an electrical plug.
  • E. powerAdapterWattage
    Indicates the electrical power capacity, in watts, that a power adapter can supply.
  • F. None of above. chosen

Provenance (4 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_69b3454f739481909ff6c28331f0c0b9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35264e44c81908dd0e0a81f1353bb completed March 12, 2026, 11:55 p.m.
PD Predicate disambiguation batch_69b34f572efc8190bad1e5078cbcb75a completed March 12, 2026, 11:42 p.m.
PDg Predicate description generation batch_69b3501834448190bedf775a80da4778 completed March 12, 2026, 11:45 p.m.
Created at: March 12, 2026, 11:19 p.m.