Triple
T1500490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temporal Key Integrity Protocol |
E29783
|
entity |
| Predicate | recommendedToBeReplacedBy |
P28179
|
FINISHED |
| Object | WPA2 with AES‑CCMP |
—
|
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: WPA2 with AES‑CCMP | Statement: [Temporal Key Integrity Protocol, recommendedToBeReplacedBy, WPA2 with AES‑CCMP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedToBeReplacedBy Context triple: [Temporal Key Integrity Protocol, recommendedToBeReplacedBy, WPA2 with AES‑CCMP]
-
A.
mayBeReplacedBy
chosen
Indicates that one entity can potentially be substituted or superseded by another entity.
-
B.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
C.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
D.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
-
E.
seeksToReplace
Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6f2d7f881909188a3e5614335cd |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.