Triple
T25535590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynamic Perspective |
E640029
|
entity |
| Predicate | SDKProvidedBy |
P125228
|
FINISHED |
| Object | Amazon |
—
|
NE NERFINISHED |
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 | Statement: [Dynamic Perspective, SDKProvidedBy, Amazon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SDKProvidedBy Context triple: [Dynamic Perspective, SDKProvidedBy, Amazon]
-
A.
clientSDKPlatform
Indicates the software platform or environment on which a client-side SDK is designed to run or be used.
-
B.
supportsAPIClientSDKs
Indicates that an entity provides or is compatible with software development kits (SDKs) intended for use by API clients.
-
C.
APIType
Indicates the type or category of an API associated with or used by an entity.
-
D.
providesFunctionalityOf
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
-
E.
hasSoftwareDevelopmentKit
chosen
Indicates that an entity provides or is associated with a software development kit (SDK) that can be used to develop, integrate, or extend its functionality.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f866376081909ab76a8aa5c3fea7 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:22 p.m.