Triple
T17556003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Traffic Management Command |
E427590
|
entity |
| Predicate | hasAlias |
P455
|
FINISHED |
| Object | MTMC |
—
|
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: MTMC | Statement: [Military Traffic Management Command, hasAlias, MTMC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MTMC Context triple: [Military Traffic Management Command, hasAlias, MTMC]
-
A.
MTMC
chosen
MTMC is the former U.S. Army command responsible for managing and coordinating the global movement of military personnel and cargo.
-
B.
MTM
MTM is the Mercury Transfer Module of the BepiColombo mission, responsible for propelling and guiding the spacecraft on its journey to Mercury.
-
C.
MTM
MTM is the company responsible for operating Melbourne’s metropolitan passenger rail network in Victoria, Australia.
-
D.
MTM
MTM is a music-focused project or group associated with the artist Mio, likely involved in collaborative releases or performances.
-
E.
MMTM
MMTM is the ICAO airport code for General Francisco Javier Mina International Airport serving Tampico, Mexico.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562357b48190bde6f49df0c983c2 |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 5:50 a.m.