Triple
T1077372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTE |
E23868
|
entity |
| Predicate | authenticationAlgorithms |
P18412
|
FINISHED |
| Object | MILENAGE |
—
|
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: MILENAGE | Statement: [LTE, authenticationAlgorithms, MILENAGE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authenticationAlgorithms Context triple: [LTE, authenticationAlgorithms, MILENAGE]
-
A.
authenticationStandard
Indicates that one entity defines, specifies, or adheres to a particular method, protocol, or set of rules for verifying the identity of another entity.
-
B.
authenticationType
chosen
Indicates the method or mechanism used to verify and confirm an entity’s identity in an interaction or system.
-
C.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
-
D.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
E.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94288d88190aae4fb86236c0702 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.