Triple
T10168284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noise_KK pattern |
E235261
|
entity |
| Predicate | initiatorKnows |
P92206
|
FINISHED |
| Object | responder 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: responder static public key | Statement: [Noise_KK pattern, initiatorKnows, responder static public key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiatorKnows Context triple: [Noise_KK pattern, initiatorKnows, responder static public key]
-
A.
initiator
Indicates the entity that starts, triggers, or causes an action, event, or process to occur.
-
B.
initiatedBy
Indicates that an action, event, or process was started or set in motion by a particular entity.
-
C.
possiblyInitiatedBy
Indicates that an event or state may have been initiated or caused by a particular entity, but this initiating role is uncertain or not definitively established.
-
D.
hasInitiation
Indicates that one entity initiates, starts, or triggers an action, process, or relationship involving another entity.
-
E.
initiationStatus
Indicates the current state or phase of beginning or starting a process, activity, or relationship between entities.
- 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_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. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.