Triple
T10682052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEAD_CHACHA20_POLY1305 |
E251780
|
entity |
| Predicate | associatedDataRole |
P95292
|
FINISHED |
| Object | authenticated but not encrypted |
—
|
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: authenticated but not encrypted | Statement: [AEAD_CHACHA20_POLY1305, associatedDataRole, authenticated but not encrypted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDataRole Context triple: [AEAD_CHACHA20_POLY1305, associatedDataRole, authenticated but not encrypted]
-
A.
associatedWithTitleHolderRole
Indicates a relationship where an entity is connected to, or linked with, a role held by a title holder.
-
B.
associatedWithAuthorRole
Indicates that an entity is connected to another entity specifically in the capacity or role of an author.
-
C.
associatedWithStationRole
Indicates that an entity has a connection or involvement with a specific role or function at a station.
-
D.
conceptualRole
Indicates the functional or semantic role that one concept plays in relation to another within a conceptual structure or system.
-
E.
antRole
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc30be481909922844b539b622d |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:10 p.m.