Triple
T27509730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playfair cipher |
E694375
|
entity |
| Predicate | mergesLetters |
P32678
|
FINISHED |
| Object | I and J |
—
|
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: I and J | Statement: [Playfair cipher, mergesLetters, I and J]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergesLetters Context triple: [Playfair cipher, mergesLetters, I and J]
-
A.
mergedBy
chosen
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
B.
mergedOrReorganized
Indicates that one entity has combined with or been structurally reorganized into another entity, resulting in a changed or unified organizational form.
-
C.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
D.
hasLettersFor
Indicates that one entity possesses or contains written correspondence intended for another entity.
-
E.
followsLetter
Indicates that one element in a sequence comes immediately after another element in alphabetical or ordered letter arrangement.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 1:15 p.m.