Triple
T11959468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMake |
E284629
|
entity |
| Predicate | supportsBuildConfiguration |
P85960
|
FINISHED |
| Object | Debug |
—
|
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: Debug | Statement: [CMake, supportsBuildConfiguration, Debug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBuildConfiguration Context triple: [CMake, supportsBuildConfiguration, Debug]
-
A.
buildConfiguration
chosen
Indicates the specific setup, options, and parameters used when building or compiling a software project.
-
B.
supportsCodeBuilder
Indicates that an entity provides compatibility with or functionality for a code-building tool or environment.
-
C.
appliesToConfiguration
Indicates that something (such as a rule, setting, or operation) is relevant to, affects, or is intended for a particular configuration.
-
D.
supportsBuildManifestFormat
Indicates that one entity is capable of handling or is compatible with a specified build manifest format used in a build process.
-
E.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9036941948190b150369094551731 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.