Triple
T21228111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMA SpecWorks |
E523134
|
entity |
| Predicate | notableSpecification |
P41883
|
FINISHED |
| Object | OMA Push |
—
|
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: OMA Push | Statement: [OMA SpecWorks, notableSpecification, OMA Push]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OMA Push Context triple: [OMA SpecWorks, notableSpecification, OMA Push]
-
A.
OMA
OMA is a renowned international architecture firm known for its innovative, often experimental designs and influential contributions to contemporary architecture.
-
B.
OMA
OMA is the IATA airport code for Eppley Airfield, the primary commercial airport serving Omaha, Nebraska.
-
C.
OMA
OMA is the ICAO airline designator assigned to Oman Air, the national carrier of Oman.
-
D.
OMA
OMA is a Mexican airport operator that manages and develops a network of airports in the central and northern regions of Mexico.
-
E.
OMA
chosen
OMA (Open Mobile Alliance) is an industry forum that develops open standards and specifications to ensure interoperability and compatibility across mobile and wireless services and devices.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734ad5068819088b203eeba4e6380 |
completed | April 21, 2026, 8:26 a.m. |
Created at: April 16, 2026, 3:44 p.m.