Triple

T2754417
Position Surface form Disambiguated ID Type / Status
Subject Airbus A318 E61065 entity
Predicate IATAMaximumPassengerCapacity P11680 FINISHED
Object 132 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: 132 | Statement: [Airbus A318, IATAMaximumPassengerCapacity, 132]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: IATAMaximumPassengerCapacity
Context triple: [Airbus A318, IATAMaximumPassengerCapacity, 132]
  • A. maximumPassengerCapacity chosen
    Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
  • B. passengerCapacityCategory
    Indicates the classification of an entity based on the number of passengers it is designed or allowed to carry.
  • C. aircraftCapacity
    Indicates the maximum number of passengers or amount of load that an aircraft is designed or allowed to carry.
  • D. designedCargoCapacity
    Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
  • E. seatingCapacity
    Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
  • 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_69ab4b7a85bc819094a349b84beb1f2c completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdb7073d081909da84b21015972f2 completed March 7, 2026, 8:01 a.m.
PD Predicate disambiguation batch_69abd82d005c81908a1ac7a1313c6d88 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:56 p.m.