Triple
T27594263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CloudEvents |
E699852
|
entity |
| Predicate | isPlatformNeutral |
P7054
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [CloudEvents, isPlatformNeutral, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlatformNeutral Context triple: [CloudEvents, isPlatformNeutral, true]
-
A.
isVendorNeutral
Indicates that something is not biased toward, affiliated with, or dependent on any particular vendor or supplier.
-
B.
platformNeutral
chosen
Indicates that something is compatible with, applicable to, or designed to work across multiple platforms without dependence on any specific one.
-
C.
isMultiplatform
Indicates that something is designed to operate or be available across multiple platforms or environments.
-
D.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
-
E.
isKeyPlatformFor
Indicates that one entity serves as a primary or foundational platform that enables, supports, or underpins the activities, services, or operations 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63056c6a08190857baf73f58aa682 |
completed | May 2, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:06 p.m.