Triple
T25932662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mantle |
E653472
|
entity |
| Predicate | influenceAspect |
P157823
|
FINISHED |
| Object | Vulkan API design |
—
|
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: Vulkan API design | Statement: [Mantle, influenceAspect, Vulkan API design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influenceAspect Context triple: [Mantle, influenceAspect, Vulkan API design]
-
A.
influencedAspectOf
chosen
Indicates that one entity has affected, shaped, or altered a particular aspect or component of another entity.
-
B.
onAspect
Indicates that one entity is positioned on a particular side, surface, or facet of another entity.
-
C.
coversAspect
Indicates that one entity addresses, includes, or deals with a particular aspect or facet of another entity or topic.
-
D.
incorporatesInfluence
Indicates that one entity integrates or absorbs the influence, ideas, or characteristics of another into itself.
-
E.
refersToAspect
Indicates that one entity specifically references or points to a particular aspect, feature, or component 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 22, 2026, 8:37 a.m.