Triple
T36671642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenEmbedded |
E905429
|
entity |
| Predicate | supportsBuildReproducibility |
P167600
|
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: [OpenEmbedded, supportsBuildReproducibility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBuildReproducibility Context triple: [OpenEmbedded, supportsBuildReproducibility, yes]
-
A.
aimsForReproducibleBuilds
chosen
Indicates that an entity intentionally works to ensure its builds can be reliably reproduced with identical results from the same source and configuration.
-
B.
supportsBuildManagement
Indicates that one entity provides functionality or assistance for managing the build process of another entity (such as compiling, packaging, and related build tasks).
-
C.
reproducibility
Indicates that an action, process, or result can be repeated under the same conditions and yield consistent, comparable outcomes.
-
D.
builtAgainst
Indicates that one structure or object is constructed directly adjoining and supported by the side or surface of another.
-
E.
supportsPreReleaseVersions
Indicates that one entity is capable of handling, accepting, or working with pre-release or non-final versions of 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.