Triple
T27590127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenStack Congress |
E699772
|
entity |
| Predicate | enforcesPolicyAcross |
P126667
|
FINISHED |
| Object | compute services |
—
|
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: compute services | Statement: [OpenStack Congress, enforcesPolicyAcross, compute services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcesPolicyAcross Context triple: [OpenStack Congress, enforcesPolicyAcross, compute services]
-
A.
appliesPolicyOn
chosen
Indicates that one entity enforces, executes, or brings into effect a specific policy on another entity or context.
-
B.
appliesPoliciesOf
Indicates that one entity enforces, follows, or implements the policies that originate from or are defined by another entity.
-
C.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
D.
containsPolicyOn
Indicates that one entity includes, references, or incorporates a specific policy within it.
-
E.
analyzesPolicy
Indicates that an entity examines, evaluates, or studies a policy to understand its implications, effectiveness, or impact.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:05 p.m.