Triple
T27781374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VPC CNI plugin |
E699342
|
entity |
| Predicate | allocatesIPFrom |
P83496
|
FINISHED |
| Object | Amazon VPC subnets |
—
|
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: Amazon VPC subnets | Statement: [VPC CNI plugin, allocatesIPFrom, Amazon VPC subnets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocatesIPFrom Context triple: [VPC CNI plugin, allocatesIPFrom, Amazon VPC subnets]
-
A.
addressAllocation
Indicates the assignment or reservation of an address (such as an IP or memory address) for use by a specific entity or resource.
-
B.
allocatesFrom
chosen
Indicates that a resource, portion, or share is assigned or taken from a specified source or pool.
-
C.
dynamicAddressAllocation
Indicates that addresses are assigned to entities dynamically at runtime rather than being fixed or statically configured.
-
D.
usesIPFrom
Indicates that one entity operates or communicates using an IP address that originates from or is assigned to another entity.
-
E.
allocates
Indicates the act of assigning or distributing resources, responsibilities, or portions of something to specific entities or purposes.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 5:10 p.m.