Triple
T4478574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.1Qch |
E100070
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | CQF |
E44307
|
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: CQF | Statement: [IEEE 802.1Qch, abbreviation, CQF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CQF Context triple: [IEEE 802.1Qch, abbreviation, CQF]
-
A.
CQF
chosen
CQF (Cyclic Queuing and Forwarding) is a time-sensitive networking mechanism defined in IEEE 802.1Qch that provides deterministic, low-latency packet forwarding using cyclic transmission queues.
-
B.
CFA
CFA is the abbreviation for Commander Field Army, the senior British Army officer responsible for commanding the Field Army’s operational forces.
-
C.
QF
QF is the IATA airline designator used for Qantas, the flag carrier of Australia.
-
D.
QEF
QEF is the IATA airport code for Frankfurt Egelsbach Airport, a general aviation airfield near Frankfurt, Germany.
-
E.
CQD
CQD was an early maritime distress signal used in wireless telegraphy before the widespread adoption of SOS.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356db0a008190ad39b68efc095b8d |
completed | March 13, 2026, 12:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b62888ea508190a052c0b2edee7fca |
completed | March 15, 2026, 3:33 a.m. |
Created at: March 12, 2026, 11:35 p.m.