Triple
T14683064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTU Maintenance |
E344835
|
entity |
| Predicate | customerType |
P809
|
FINISHED |
| Object | OEMs |
E660946
|
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: OEMs | Statement: [MTU Maintenance, customerType, OEMs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OEMs Context triple: [MTU Maintenance, customerType, OEMs]
-
A.
OEMs
chosen
OEMs (Original Equipment Manufacturers) are companies that design and produce vehicles or other end products into which components and technologies from suppliers like Mobileye are integrated.
-
B.
OEM
OEM refers to the Office for Emergency Management, a U.S. government agency created during World War II to coordinate civilian defense and federal emergency preparedness activities.
-
C.
OEMA
OEMA is the ICAO airport code for Prince Mohammad bin Abdulaziz International Airport serving Medina in Saudi Arabia.
-
D.
SF OEM
SF OEM is the abbreviated name for the San Francisco Office of Emergency Management, the city agency responsible for coordinating preparedness, response, and recovery efforts during emergencies and disasters.
-
E.
San Francisco OEM
San Francisco OEM is the city’s Office of Emergency Management, responsible for coordinating preparedness, response, and recovery efforts for disasters and major incidents in San Francisco.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde18592088190892ae1cc371165be |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:28 a.m.