Triple
T4769033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atbash |
E105879
|
entity |
| Predicate | informationPreservation |
P40904
|
FINISHED |
| Object | lossless transformation |
—
|
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: lossless transformation | Statement: [Atbash, informationPreservation, lossless transformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationPreservation Context triple: [Atbash, informationPreservation, lossless transformation]
-
A.
preservationPurpose
Indicates that something exists, is created, or is maintained with the specific aim of preserving or safeguarding another entity or resource.
-
B.
preservationType
chosen
Indicates the method or process by which something is preserved or kept from deterioration.
-
C.
preservationMethod
Indicates the technique or process used to maintain, protect, or prolong the condition, quality, or usability of something over time.
-
D.
preservationFocus
Indicates that the primary concern or emphasis is on maintaining, protecting, or conserving something in its existing or intended state.
-
E.
reasonForPreservation
Indicates that something is being preserved or maintained for a particular reason, purpose, or justification.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.