Triple
T6169419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griffith Airport |
E137652
|
entity |
| Predicate | pushpinLabel |
P9248
|
FINISHED |
| Object | YGGF |
E573124
|
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: YGGF | Statement: [Griffith Airport, pushpinLabel, YGGF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YGGF Context triple: [Griffith Airport, pushpinLabel, YGGF]
-
A.
YGGF
chosen
YGGF is the ICAO airport code assigned to Griffith Airport in New South Wales, Australia.
-
B.
Givors
Givors is a commune in eastern France located in the Metropolis of Lyon, known historically as an industrial and river-port town on the Rhône.
-
C.
Gŵyr
Gŵyr is the Welsh name for the Gower Peninsula, a scenic coastal region in southwest Wales renowned for its beaches, cliffs, and natural beauty.
-
D.
Frey
Frey is a Norse god associated with fertility, prosperity, and fair weather, often linked to kingship and peace in Norse mythology.
-
E.
Frey
Frey is the central protagonist of the game Elysium, around whom the story’s main events and character development revolve.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d8de56481909583104c70a52616 |
completed | March 22, 2026, 9:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c16ee938748190ad03e19c241b0881 |
completed | March 23, 2026, 4:48 p.m. |
Created at: March 22, 2026, 4:18 p.m.