Triple
T12514129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | name service switch |
E299153
|
entity |
| Predicate | configuredPerDatabase |
P105358
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [name service switch, configuredPerDatabase, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configuredPerDatabase Context triple: [name service switch, configuredPerDatabase, yes]
-
A.
hasDatabase
Indicates that an entity possesses, uses, or is associated with a specific database.
-
B.
usedInDatabases
Indicates that something is employed or implemented within one or more database systems or database contexts.
-
C.
statusInDatabases
Indicates the current state or condition an entity has within one or more database systems.
-
D.
hasOnlineDatabases
Indicates that an entity maintains or provides access to one or more databases that are available online.
-
E.
supportsDatabaseAbstraction
Indicates that one entity provides or enables a database abstraction layer for another, allowing interaction with databases independently of specific database implementations.
- F. None of above. chosen
Provenance (4 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954b715fc819091fa84430be46273 |
completed | April 10, 2026, 7:51 p.m. |
Created at: April 8, 2026, 9:57 p.m.