Triple
T29900077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JavaBeans |
E759384
|
entity |
| Predicate | supportsToolIntegration |
P66291
|
FINISHED |
| Object | bean introspection APIs |
—
|
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: bean introspection APIs | Statement: [JavaBeans, supportsToolIntegration, bean introspection APIs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsToolIntegration Context triple: [JavaBeans, supportsToolIntegration, bean introspection APIs]
-
A.
supportsInstruction
Indicates that one entity provides assistance, resources, or functionality that enables or facilitates the instruction or teaching activities of another entity.
-
B.
supportsPocketIntegration
Indicates that an entity is compatible with and can integrate functionality with the Pocket service.
-
C.
includesTooling
chosen
Indicates that one entity contains, provides, or comes bundled with specific tools or tooling capabilities related to another entity.
-
D.
supportsTransportIntegrationWith
Indicates that one entity enables or is compatible with the integration of transport or transportation-related systems, services, or data with another entity.
-
E.
supportsBackupTool
Indicates that one entity provides compatibility with or functionality for a specified backup tool.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:06 p.m.