Triple
T36126355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babington Plot |
E1044889
|
entity |
| Predicate | involvedCommunicationMethod |
P2798
|
FINISHED |
| Object | ciphered letters |
—
|
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: ciphered letters | Statement: [Babington Plot, involvedCommunicationMethod, ciphered letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedCommunicationMethod Context triple: [Babington Plot, involvedCommunicationMethod, ciphered letters]
-
A.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
B.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
-
C.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
D.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
E.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:08 p.m.