Triple
T525306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LFPG |
E10903
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | LFPG |
E10903
|
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: LFPG | Statement: [LFPG, ICAOcode, LFPG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LFPG Context triple: [LFPG, ICAOcode, LFPG]
-
A.
LFPG
chosen
LFPG is the ICAO airport code for Paris Charles de Gaulle Airport, France’s largest and busiest international air hub.
-
B.
LFPB
LFPB is the ICAO airport code for Paris–Le Bourget Airport, a historic airfield near Paris known for business aviation and the Paris Air Show.
-
C.
LFPO
LFPO is the ICAO airport code for Paris Orly Airport, a major international airport serving the Paris metropolitan area in France.
-
D.
PLAF
PLAF is an abbreviation commonly used to refer to the Polish Air Force, the air warfare branch of Poland’s armed forces.
-
E.
DFG
DFG is Germany’s central self-governing research funding organization, supporting scientific and academic research across all disciplines.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b7f448819087e5e7f3b37d7142 |
completed | Feb. 28, 2026, 1:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4b5d71fa881908c52d2a675b5b7d1 |
completed | March 1, 2026, 9:55 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.