Triple
T27583015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domino servlet engine |
E699627
|
entity |
| Predicate | accessesDataStore |
P141566
|
FINISHED |
| Object | Domino NSF databases |
—
|
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: Domino NSF databases | Statement: [Domino servlet engine, accessesDataStore, Domino NSF databases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesDataStore Context triple: [Domino servlet engine, accessesDataStore, Domino NSF databases]
-
A.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
B.
dataAccessModel
Indicates the framework or scheme that governs how data can be accessed, including who can retrieve it, under what conditions, and through which mechanisms.
-
C.
usesDataSystem
chosen
Indicates that one entity employs, accesses, or relies on a particular data system to perform its functions or operations.
-
D.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
E.
supportsDatastoreType
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of datastore.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 2:03 p.m.