Triple
T24027435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmonic |
E595003
|
entity |
| Predicate | corePlatform |
P154313
|
FINISHED |
| Object | wasmCloud |
—
|
NE NERFINISHED |
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: wasmCloud | Statement: [Cosmonic, corePlatform, wasmCloud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corePlatform Context triple: [Cosmonic, corePlatform, wasmCloud]
-
A.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
-
B.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
-
C.
typicalPlatform
Indicates that something commonly or usually serves as the platform or environment on which another thing operates, appears, or is based.
-
D.
isKeyPlatformFor
chosen
Indicates that one entity serves as a primary or foundational platform that enables, supports, or underpins the activities, services, or operations of another entity.
-
E.
coreBasedOn
Indicates that one entity is fundamentally derived from, built upon, or primarily based on 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76d393c8190ae9b1b9e43fe0efa |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:54 p.m.