Triple
T12514139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | name service switch |
E299153
|
entity |
| Predicate | lookupOrderDefinedIn |
P23699
|
FINISHED |
| Object | /etc/nsswitch.conf |
—
|
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: /etc/nsswitch.conf | Statement: [name service switch, lookupOrderDefinedIn, /etc/nsswitch.conf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lookupOrderDefinedIn Context triple: [name service switch, lookupOrderDefinedIn, /etc/nsswitch.conf]
-
A.
associatedOrderFoundedIn
Indicates that an order or organization associated with an entity was founded in a specified place or time.
-
B.
areDefinedIn
chosen
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
C.
orderFoundedBy
Indicates that a particular order or organization was established or created by a specific person or entity.
-
D.
orderFoundedIn
Indicates the place or location where an order (such as a religious, military, or organizational order) was originally established or founded.
-
E.
scopeDefinedBy
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained 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_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. |
Created at: April 8, 2026, 9:57 p.m.