Triple
T12638735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gombe Airport |
E301834
|
entity |
| Predicate | NDBIdentifier |
P3732
|
FINISHED |
| Object | GM |
—
|
LITERAL 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: GM | Statement: [Gombe Airport, NDBIdentifier, GM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NDBIdentifier Context triple: [Gombe Airport, NDBIdentifier, GM]
-
A.
GNDID
Indicates a standardized authority identifier linking an entity to its unique record in the Gemeinsame Normdatei (GND) authority file.
-
B.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
NATODesignation
Indicates that one entity is the official name or code assigned to another entity by NATO for identification or classification purposes.
-
D.
GNISID
Indicates that an entity is associated with a specific identifier from the U.S. Geographic Names Information System (GNIS), uniquely linking it to an official geographic feature record.
-
E.
nebulaType
Indicates the specific classification or category of a nebula based on its physical and observational characteristics.
- F. None of above.
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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:16 p.m.