Triple
T32710084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DataNucleus |
E836373
|
entity |
| Predicate | supportsDatastore |
P11254
|
FINISHED |
| Object | RDBMS |
—
|
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: RDBMS | Statement: [DataNucleus, supportsDatastore, RDBMS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDatastore Context triple: [DataNucleus, supportsDatastore, RDBMS]
-
A.
supportsDatastoreType
chosen
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of datastore.
-
B.
supportsBlockStorage
Indicates that one entity provides or is compatible with block-level storage capabilities for another entity.
-
C.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
-
D.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
-
E.
supportsKeyStorage
Indicates that an entity is capable of securely storing cryptographic keys or similar sensitive key material.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:10 a.m.