Triple

T1991789
Position Surface form Disambiguated ID Type / Status
Subject Philippine Airlines E43266 entity
Predicate IATAcode P418 FINISHED
Object PR E662 NE 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: PR | Statement: [Philippine Airlines, IATAcode, PR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PR
Context triple: [Philippine Airlines, IATAcode, PR]
  • A. PR chosen
    PR is the two-letter postal abbreviation commonly used to refer to Puerto Rico, a Caribbean island and unincorporated territory of the United States.
  • B. PAR
    PAR is the IATA city code representing the collective airport system serving Paris, France, including major airports such as Charles de Gaulle and Orly.
  • C. POR
    POR is the three-letter FIFA country code used to represent the Portugal national football team in international competitions and rankings.
  • D. P
    P is the vehicle registration code used on license plates for the Czech city of Plzeň.
  • E. PL
    PL is the commonly used abbreviation for the Patriot League, an NCAA Division I collegiate athletic conference known for emphasizing both academic and athletic excellence.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a88714cf2c819081644be450b8356e completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb846f1c0819081edd8d5eb59adce completed March 7, 2026, 5:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae0338631c8190a8c7e5177ac473a8 completed March 8, 2026, 11:16 p.m.
Created at: March 4, 2026, 7:37 p.m.