Triple
T19749746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infrastructure as a Service |
E474345
|
entity |
| Predicate | layerInStack |
P33683
|
FINISHED |
| Object | infrastructure layer |
—
|
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: infrastructure layer | Statement: [Infrastructure as a Service, layerInStack, infrastructure layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layerInStack Context triple: [Infrastructure as a Service, layerInStack, infrastructure layer]
-
A.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
B.
layerNumber
Indicates the specific position or index of a layer within an ordered stack or layered structure.
-
C.
isStackedWith
Indicates that one object is positioned directly on top of or beneath another object so that they form a vertical stack together.
-
D.
layerType
Indicates the specific kind or category of layer that an entity belongs to or is classified as.
-
E.
layerStructure
chosen
Indicates a relationship where one entity is organized in or assigned to a specific layer or hierarchical level within a structured system.
- 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.