Triple
T26098014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akamai Technologies |
E658324
|
entity |
| Predicate | hasDataCenterType |
P96706
|
FINISHED |
| Object | edge servers |
—
|
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: edge servers | Statement: [Akamai Technologies, hasDataCenterType, edge servers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataCenterType Context triple: [Akamai Technologies, hasDataCenterType, edge servers]
-
A.
supportsDataCenterAbstraction
Indicates that one entity provides or enables an abstraction layer for representing or managing data center resources or functionality.
-
B.
hasCenterType
chosen
Indicates that something is characterized by or assigned a specific type or category of center.
-
C.
dataCenterLocation
Indicates the geographical or physical location where a data center is situated or hosted.
-
D.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
E.
hasRAndDCenterIn
Indicates that an entity maintains a research and development (R&D) center located in a specified place.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 7:52 p.m.