Triple
T19750318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud Enterprise Network |
E474355
|
entity |
| Predicate | availabilityFeature |
P55186
|
FINISHED |
| Object | high availability 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: high availability design | Statement: [Cloud Enterprise Network, availabilityFeature, high availability design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availabilityFeature Context triple: [Cloud Enterprise Network, availabilityFeature, high availability design]
-
A.
availabilityType
Indicates the specific way in which something is available or offered (e.g., its mode, status, or conditions of availability) in relation to another entity.
-
B.
availabilityModel
chosen
Indicates how and under what conditions an entity is available for use, access, or interaction.
-
C.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
D.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
E.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529875688190952af476aa5be492 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.