Triple
T29739212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MQCB |
E752548
|
entity |
| Predicate | callbackTypeExample |
P163165
|
FINISHED |
| Object | MQCBT_MESSAGE_CONSUMER |
—
|
LITERAL 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: MQCBT_MESSAGE_CONSUMER | Statement: [MQCB, callbackTypeExample, MQCBT_MESSAGE_CONSUMER]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callbackTypeExample Context triple: [MQCB, callbackTypeExample, MQCBT_MESSAGE_CONSUMER]
-
A.
callbackType
chosen
Indicates the specific kind or category of callback event or function associated with an entity or interaction.
-
B.
exampleType
Indicates that one entity serves as a representative or illustrative instance of the type or category defined by another entity.
-
C.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
D.
hookType
Indicates the specific kind or category of hook associated with or used by an entity.
-
E.
codeExample
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
- F. None of above.
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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67336d44881908c3580e1ebb15bcf |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:47 p.m.