Triple
T1500489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temporal Key Integrity Protocol |
E29783
|
entity |
| Predicate | configurationOptionIn |
P28533
|
FINISHED |
| Object | Wi‑Fi access points |
—
|
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: Wi‑Fi access points | Statement: [Temporal Key Integrity Protocol, configurationOptionIn, Wi‑Fi access points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationOptionIn Context triple: [Temporal Key Integrity Protocol, configurationOptionIn, Wi‑Fi access points]
-
A.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
B.
scopeOption
Indicates that one entity specifies or constrains the range, extent, or applicability (scope) of another entity as an available option or setting.
-
C.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
D.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
E.
optimizationType
Indicates the specific strategy or method used to improve performance or efficiency within a given process or system.
- 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_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. |
| PDg | Predicate description generation | batch_69a4c4feea448190b2b5071b28a5b608 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8:12 p.m.