Triple
T18553243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAE |
E453434
|
entity |
| Predicate | deployedSince |
P132136
|
FINISHED |
| Object | around 2018 with WPA3 introduction |
—
|
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: around 2018 with WPA3 introduction | Statement: [SAE, deployedSince, around 2018 with WPA3 introduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deployedSince Context triple: [SAE, deployedSince, around 2018 with WPA3 introduction]
-
A.
deployedFor
Indicates that one entity is deployed or put into operational use to serve, support, or act on behalf of another entity.
-
B.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
C.
deployedTo
Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
-
D.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
E.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
- F. None of above. chosen
Provenance (4 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538027b94819082a4c4af66e170d7 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:38 a.m.