Triple
T20743366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collected Poems in English |
E510499
|
entity |
| Predicate | hasTranslationType |
P20094
|
FINISHED |
| Object | English translation |
—
|
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: English translation | Statement: [Collected Poems in English, hasTranslationType, English translation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTranslationType Context triple: [Collected Poems in English, hasTranslationType, English translation]
-
A.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
-
B.
hasTransliterationType
Indicates the type or system of transliteration used to convert text from one writing system into another.
-
C.
typeOfTranslation
chosen
Indicates that one entity is a specific kind or category of translation in relation to another entity.
-
D.
hasTranslationBase
Indicates that one entity serves as the original source or base text from which the other entity is translated.
-
E.
hasLanguageType
Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c210a2c08190bd767df3188bb401 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:33 p.m.