Triple

T3787241
Position Surface form Disambiguated ID Type / Status
Subject MIL-STD-1553 databus E85556 entity
Predicate busAccessControl P15393 FINISHED
Object centrally controlled by bus controller 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: centrally controlled by bus controller | Statement: [MIL-STD-1553 databus, busAccessControl, centrally controlled by bus controller]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: busAccessControl
Context triple: [MIL-STD-1553 databus, busAccessControl, centrally controlled by bus controller]
  • A. controlsAccessTo chosen
    Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
  • B. hasEntranceControl
    Indicates that an entity implements or is subject to mechanisms that regulate or control access to its entrance.
  • C. vehicleAccess
    Indicates that one entity is permitted to use, enter, or otherwise access a particular vehicle.
  • D. fareControl
    Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
  • E. passengerAccess
    Indicates that a passenger is allowed to enter, use, or move through a particular vehicle, area, or transportation-related facility.
  • 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_69aed937fa8881908208ef3801060826 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee634c6ac819099653c660c286746 completed March 9, 2026, 3:24 p.m.
PD Predicate disambiguation batch_69aee3d3c92c819081d9d5c45ef37a5d completed March 9, 2026, 3:14 p.m.
Created at: March 9, 2026, 3:13 p.m.