Triple
T10168285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noise_KK pattern |
E235261
|
entity |
| Predicate | responderKnows |
P22660
|
FINISHED |
| Object | initiator static public key |
—
|
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: initiator static public key | Statement: [Noise_KK pattern, responderKnows, initiator static public key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responderKnows Context triple: [Noise_KK pattern, responderKnows, initiator static public key]
-
A.
knows
chosen
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
B.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
C.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
D.
respondentStatus
Indicates the current role, condition, or state of a respondent in relation to a survey, inquiry, or legal/administrative process.
-
E.
answeredBy
Indicates that a question, request, or problem is responded to or resolved by a particular 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6f64a48190883aefce58a65ca6 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.