Triple
T5909050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal E |
E131414
|
entity |
| Predicate | hasIATAAirport |
P17503
|
FINISHED |
| Object | PHL |
E127980
|
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: PHL | Statement: [Terminal E, hasIATAAirport, PHL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PHL Context triple: [Terminal E, hasIATAAirport, PHL]
-
A.
PHL
chosen
PHL is the three-letter IATA airport code for Philadelphia International Airport, the primary commercial airport serving the Philadelphia metropolitan area in Pennsylvania, USA.
-
B.
PHI
PHI is the standard abbreviation used for the NBA’s Philadelphia 76ers.
-
C.
PHI
PHI is the standard abbreviation used for California Points of Historical Interest, a state-level designation for sites of local historical significance.
-
D.
.phl
.phl is a proposed or lesser-used internet country code top-level domain associated with the Philippines, distinct from its primary ccTLD, .ph.
-
E.
Logik
Logik is a foundational work on formal logic by German philosopher and mathematician Gottlob Frege, contributing significantly to the development of modern logic and the philosophy of language.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03775590481909a797b166fbe108c |
completed | March 22, 2026, 6:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b16f568081908839cd2403b7534c |
completed | March 23, 2026, 3:20 a.m. |
Created at: March 22, 2026, 3:59 p.m.