Triple
T27588340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RabbitMQ |
E699737
|
entity |
| Predicate | supportsLanguageClient |
P81836
|
FINISHED |
| Object | Java |
—
|
NE NERFINISHED |
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: Java | Statement: [RabbitMQ, supportsLanguageClient, Java]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLanguageClient Context triple: [RabbitMQ, supportsLanguageClient, Java]
-
A.
supportsLanguageClientLibrary
chosen
Indicates that an entity provides or is compatible with a client library for interacting with a specific programming language.
-
B.
supportsLanguageVersion
Indicates that one entity provides compatibility with, or can correctly operate using, a specified version of a language.
-
C.
supportsLanguageMode
Indicates that one entity provides or is compatible with a particular language mode used or required by another entity.
-
D.
supportsExtensionLanguage
Indicates that one entity provides compatibility with or functionality for a specified extension language used by another entity.
-
E.
usesLanguageSupport
Indicates that one entity makes use of language-related assistance, features, or services provided by 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: April 27, 2026, 2:05 p.m.