Triple
T3918352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGSS |
E88898
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | STN |
E88897
|
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: STN | Statement: [EGSS, IATACode, STN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STN Context triple: [EGSS, IATACode, STN]
-
A.
STN
chosen
STN is the three-letter IATA airport code for London Stansted Airport, a major international airport serving the London area in the United Kingdom.
-
B.
STN International
STN International is a professional online scientific and technical information service widely used for advanced literature and patent searching in chemistry and related fields.
-
C.
STC
STC is the commonly used abbreviation for RAF Strike Command, the former major operational command of the Royal Air Force responsible for the UK’s air combat forces.
-
D.
ST
ST is the common abbreviation for Sound Transit, the regional public transit agency serving the Seattle metropolitan area in Washington State.
-
E.
ST
ST is the commonly used abbreviation for SkyTeam, a major global airline alliance.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeed59485c819095c58edd053e3401 |
completed | March 9, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b52864e0488190ab348a52cb9168b9 |
completed | March 14, 2026, 9:20 a.m. |
Created at: March 9, 2026, 3:22 p.m.