Triple
T28893795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nesite language |
E732783
|
entity |
| Predicate | keyDecipherer |
P87147
|
FINISHED |
| Object | Bedřich Hrozný |
—
|
NE NERFINISHED |
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: Bedřich Hrozný | Statement: [Nesite language, keyDecipherer, Bedřich Hrozný]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyDecipherer Context triple: [Nesite language, keyDecipherer, Bedřich Hrozný]
-
A.
coDecipherer
Indicates that two or more entities jointly participated in deciphering or decoding something together.
-
B.
deciphers
chosen
Indicates the action of successfully interpreting or figuring out the meaning of something that is difficult to understand or encoded.
-
C.
cipherKey
Indicates that one entity serves as the cryptographic key used to encrypt or decrypt information associated with another entity.
-
D.
keyDecree
Indicates that an authoritative or foundational decree, order, or ruling is issued, establishing a key directive or rule in a given context.
-
E.
keyIdentifier
Indicates that one entity serves as a unique key or identifying code used to distinguish or reference another 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa1fe148190bf4e4f3f8c5adc47 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:57 a.m.