Triple
T8945846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turbo C++ |
E213218
|
entity |
| Predicate | compilationModel |
P4975
|
FINISHED |
| Object | native code compilation |
—
|
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: native code compilation | Statement: [Turbo C++, compilationModel, native code compilation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilationModel Context triple: [Turbo C++, compilationModel, native code compilation]
-
A.
compilationType
chosen
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
B.
compilationScope
Indicates the range or set of elements (such as files, modules, or code units) that are included and processed together during a compilation process.
-
C.
compilationAppearance
Indicates that an entity appears as part of a compilation, such as being included within a collected or aggregated work.
-
D.
compilationStatus
Indicates the current state or outcome of a compilation process for a given entity (e.g., whether it is pending, in progress, successful, or failed).
-
E.
compiledTo
Indicates that one artifact (such as source code) has been transformed into another, typically lower-level or executable form, through a compilation process.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66dd00c481908ff20fd66c1954cc |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.