Triple
T10020137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MessageProducer interface |
E200591
|
entity |
| Predicate | supportsDestinationType |
P30653
|
FINISHED |
| Object | Queue |
—
|
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: Queue | Statement: [MessageProducer interface, supportsDestinationType, Queue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDestinationType Context triple: [MessageProducer interface, supportsDestinationType, Queue]
-
A.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
servesDestinationType
chosen
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
D.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
E.
supportsTestType
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd777b208190ad75eac79eec0c2f |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.