Triple
T18831284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cessnock Airport |
E460535
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | CES |
—
|
NE NERFINISHED |
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: CES | Statement: [Cessnock Airport, IATA code, CES]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CES Context triple: [Cessnock Airport, IATA code, CES]
-
A.
CES
CES is the commonly used abbreviation for the U.S. Committee on Economic Security, the New Deal–era body that helped design foundational social welfare programs like Social Security.
-
B.
CES
CES is the Center for Entrepreneurial Studies, an academic hub focused on research, education, and support for entrepreneurship and innovation.
-
C.
CES
CES is the ICAO airline designator used to identify China Eastern Airlines in international aviation operations.
-
D.
CES
CES is the station code used to identify Cessnock subway station on the Glasgow Subway network.
-
E.
CES
chosen
CES is the IATA airport code for Cessnock Airport, a regional airport serving the Cessnock area in New South Wales, Australia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a9992bb081908ba517a5c9d93ef3 |
completed | April 20, 2026, 4:20 a.m. |
Created at: April 10, 2026, 11:56 a.m.