Triple
T27663294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Config Controller |
E697172
|
entity |
| Predicate | configurationSource |
P91057
|
FINISHED |
| Object | central repository |
—
|
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: central repository | Statement: [Config Controller, configurationSource, central repository]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationSource Context triple: [Config Controller, configurationSource, central repository]
-
A.
configurationLocation
Indicates the place or context where a configuration is stored, applied, or defined.
-
B.
carbonSource
Indicates that one entity serves as the source or provider of carbon for another entity or process.
-
C.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
D.
deploymentSource
Indicates the origin or mechanism from which something is deployed, such as the system, process, or source responsible for initiating the deployment.
-
E.
configurationVia
chosen
Indicates that one entity is set up, customized, or controlled through another entity serving as its configuration mechanism or source.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 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:37 p.m.