Triple
T1160836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ChakraCore |
E24485
|
entity |
| Predicate | supportsEmbedding |
P5376
|
FINISHED |
| Object | C++ applications |
—
|
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: C++ applications | Statement: [ChakraCore, supportsEmbedding, C++ applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEmbedding Context triple: [ChakraCore, supportsEmbedding, C++ applications]
-
A.
canBeEmbeddedIn
chosen
Indicates that one entity can be inserted or integrated within another entity, typically preserving structure or compatibility.
-
B.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
supportedAct
Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
-
E.
supportsView
Indicates that one entity provides the capability to display, render, or present another entity in a particular view or format.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcaf3a9081908bad2eba74dffbc1 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.