Triple
T27594276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CloudEvents |
E699852
|
entity |
| Predicate | stableVersion |
P135209
|
FINISHED |
| Object | 1.0 |
—
|
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: 1.0 | Statement: [CloudEvents, stableVersion, 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stableVersion Context triple: [CloudEvents, stableVersion, 1.0]
-
A.
stableReleaseStatus
Indicates the release status or condition of a stable version of something (such as software or a product).
-
B.
lastStableVersion
chosen
Indicates the most recent version of an entity that is considered stable and suitable for general use.
-
C.
continuousVersionName
Indicates that one entity is the name or label assigned to a continuous or ongoing version of another entity.
-
D.
liveVersionReleasedOn
Indicates the date or time when a live version of something (such as a product, feature, or content) is officially released or made available.
-
E.
stableReleaseRepository
Indicates that the referenced software artifact is stored in, or distributed through, a repository designated for stable (non-experimental) releases.
- 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.