Triple
T10951288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GEE-H |
E258731
|
entity |
| Predicate | hasAbbreviationForm |
P43
|
FINISHED |
| Object | GEE-H |
E258731
|
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: GEE-H | Statement: [GEE-H, hasAbbreviationForm, GEE-H]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GEE-H Context triple: [GEE-H, hasAbbreviationForm, GEE-H]
-
A.
GEE-H
chosen
GEE-H is a successor model to the Gee language model series, representing a more advanced generation of the system.
-
B.
GEE
GEE is a World War II–era British airborne radio navigation system used to improve the accuracy of bombing and navigation missions.
-
C.
Gee
Gee was a World War II-era British radio navigation system that enabled Royal Air Force bombers to determine their position and improve bombing accuracy, especially during night operations.
-
D.
GEC
GEC is the ICAO airline designator used by Lufthansa Cargo, the air freight division of Lufthansa.
-
E.
GEG
GEG is the three-letter IATA airport code for Spokane International Airport in Spokane, Washington.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770fc156c8190826e124c13ce7242 |
completed | April 9, 2026, 9:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e23c57038c819087671177c2ed5633 |
completed | April 17, 2026, 1:57 p.m. |
Created at: April 8, 2026, 9:23 p.m.