Triple

T23265192
Position Surface form Disambiguated ID Type / Status
Subject JMB Premier E588126 entity
Predicate serviceClassRelevance P5621 FINISHED
Object economy class passengers 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: economy class passengers | Statement: [JMB Premier, serviceClassRelevance, economy class passengers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: serviceClassRelevance
Context triple: [JMB Premier, serviceClassRelevance, economy class passengers]
  • A. serviceClass chosen
    Indicates the classification or category of service associated with or provided by an entity in the relationship.
  • B. servicePatternOf
    Indicates that one entity is the service pattern (e.g., schedule, routing, or operational configuration) that defines or characterizes how another service-related entity operates.
  • C. serviceFor
    Indicates that one entity provides a service or performs functions on behalf of another entity.
  • D. servicePatternInfluenced
    Indicates that the characteristics or structure of a service pattern are affected or shaped by another factor, entity, or condition.
  • E. serviceClassAccess
    Indicates that one entity is permitted to use or interact with a particular class or category of service provided by another entity.
  • 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_69e25d148adc819088efbf42672604e9 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f194cc3b908190aaefd036aa2b52b5 completed April 29, 2026, 5:19 a.m.
PD Predicate disambiguation batch_69effce4d704819092826931d430e8c4 completed April 28, 2026, 12:18 a.m.
Created at: April 17, 2026, 4:34 p.m.