Triple
T27799367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spooling Directory Source |
E702196
|
entity |
| Predicate | configurationProperty |
P86411
|
FINISHED |
| Object | spoolDir |
—
|
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: spoolDir | Statement: [Spooling Directory Source, configurationProperty, spoolDir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationProperty Context triple: [Spooling Directory Source, configurationProperty, spoolDir]
-
A.
configurableProperty
chosen
Indicates that an entity has a setting or attribute whose value can be adjusted or customized, typically to modify its behavior or characteristics.
-
B.
configurationPropagatedTo
Indicates that a specific configuration has been transmitted and applied from one entity to another.
-
C.
configurationName
Indicates the specific label or identifier assigned to a particular configuration setting or setup.
-
D.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
E.
configurationOptionIn
Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 5:33 p.m.