Triple
T29739229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MQCB |
E752548
|
entity |
| Predicate | canRegister |
P29001
|
FINISHED |
| Object | multiple callbacks on a single connection |
—
|
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: multiple callbacks on a single connection | Statement: [MQCB, canRegister, multiple callbacks on a single connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRegister Context triple: [MQCB, canRegister, multiple callbacks on a single connection]
-
A.
supportsRegistration
chosen
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
B.
registrationFor
Indicates a relationship where one entity is enrolled, signed up, or formally recorded to participate in, use, or be associated with another entity (such as an event, service, or program).
-
C.
mustRegisterWith
Indicates that one entity is required or obligated to formally enroll or record its information with another entity or authority.
-
D.
canSign
Indicates that an entity has the authority or capability to sign a document, agreement, or similar item.
-
E.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
- 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.