Triple

T11910187
Position Surface form Disambiguated ID Type / Status
Subject S7 stock (DLR type) E283372 entity
Predicate isAutonomousOperationCompatible P102306 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: [S7 stock (DLR type), isAutonomousOperationCompatible, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isAutonomousOperationCompatible
Context triple: [S7 stock (DLR type), isAutonomousOperationCompatible, yes]
  • A. autonomousFor
    Indicates that one entity operates or makes decisions independently on behalf of, or in place of, another specified context, system, or agent.
  • B. hasAutonomousMovement
    Indicates that an entity is capable of moving on its own without direct external control or intervention.
  • C. mayBeOperatedBy
    Indicates that an entity has the potential or permission to be operated, controlled, or run by another entity.
  • D. hasAutonomyOver
    Indicates that one entity possesses independent control, decision-making power, or self-governance with respect to another entity or domain.
  • E. hasAutonomyWithin
    Indicates that one entity possesses independent decision-making power or self-governance within the scope, domain, or boundaries defined by another entity.
  • 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_69d6ab2c07e88190ba13b0d21fd6cf33 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8e5278eb081909a7ecfe38beeeda9 completed April 10, 2026, 11:55 a.m.
PD Predicate disambiguation batch_69d8bb3632ac8190b13e53c2b5db7125 completed April 10, 2026, 8:56 a.m.
PDg Predicate description generation batch_69d8dd0ba0f88190b7d5e358c27ca184 completed April 10, 2026, 11:20 a.m.
Created at: April 8, 2026, 9:44 p.m.