Triple
T8728658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CICS Transaction Server |
E207195
|
entity |
| Predicate | supportsStandard |
P1587
|
FINISHED |
| Object | MQ |
E216287
|
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: MQ | Statement: [CICS Transaction Server, supportsStandard, MQ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MQ Context triple: [CICS Transaction Server, supportsStandard, MQ]
-
A.
MQ
MQ is a German vehicle registration code assigned to the Saalekreis district in the state of Saxony-Anhalt.
-
B.
MQ
chosen
MQ is IBM's messaging middleware that enables reliable, asynchronous communication between distributed applications and systems.
-
C.
MQ
MQ is the IATA airline designator used by American Eagle Airlines for its flight operations.
-
D.
MQT
MQT is the IATA airport code for Sawyer International Airport, a public airport serving the Marquette, Michigan area in the United States.
-
E.
PMQ
PMQ is a revitalized creative hub and design center in Hong Kong’s Central District, housed in the former Police Married Quarters and now home to studios, shops, and cultural events.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d1890e0819088b271db51faa738 |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf2923abc48190a5b6027c2e4f1db7 |
completed | April 3, 2026, 2:42 a.m. |
Created at: March 30, 2026, 6:37 p.m.