Triple
T29047294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Prison |
E735168
|
entity |
| Predicate | hasTitleTranslationDirection |
P20095
|
FINISHED |
| Object | Persian-to-English |
—
|
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: Persian-to-English | Statement: [Book of Prison, hasTitleTranslationDirection, Persian-to-English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleTranslationDirection Context triple: [Book of Prison, hasTitleTranslationDirection, Persian-to-English]
-
A.
hasDirectionTitle
Indicates that an entity holds the role or position of director, as specified by a particular title.
-
B.
translationDirection
chosen
Indicates the source and target languages involved in a translation, specifying the direction from the original language to the translated language.
-
C.
hasTitleInTransliteration
Indicates that an entity has a specific title represented in a transliterated form from another writing system.
-
D.
hasTitleInLanguage
Indicates that an entity has a specific title expressed in a particular language.
-
E.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 28, 2026, 10:06 a.m.