Triple

T685834
Position Surface form Disambiguated ID Type / Status
Subject Beijing Daxing International Airport E13280 entity
Predicate designedPassengerCapacity P11680 FINISHED
Object 72 million passengers per year 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: 72 million passengers per year | Statement: [Beijing Daxing International Airport, designedPassengerCapacity, 72 million passengers per year]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedPassengerCapacity
Context triple: [Beijing Daxing International Airport, designedPassengerCapacity, 72 million passengers per year]
  • A. maximumPassengerCapacity chosen
    Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
  • B. seatingCapacity
    Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
  • C. hasCrewCapacity
    Indicates that an entity is capable of accommodating a specified number of crew members.
  • D. passengersCountApproximate
    Indicates that the number of passengers involved is given as an approximate or estimated count rather than an exact figure.
  • E. crewCountApproximate
    Indicates that the relationship specifies an estimated or approximate number of crew members associated with an 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_69a4933e0f98819097d22766c49b61b8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a0f55f7481909e052a25bd12d455 completed March 1, 2026, 8:26 p.m.
PD Predicate disambiguation batch_69a49d2048d48190ab99ab59accb6909 completed March 1, 2026, 8:10 p.m.
Created at: March 1, 2026, 7:36 p.m.