Triple
T30107755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poem 85 (Odi et amo) |
E765176
|
entity |
| Predicate | commonlyTranslatedAs |
P43484
|
FINISHED |
| Object | I hate and I love |
—
|
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 hate and I love | Statement: [Poem 85 (Odi et amo), commonlyTranslatedAs, I hate and I love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyTranslatedAs Context triple: [Poem 85 (Odi et amo), commonlyTranslatedAs, I hate and I love]
-
A.
alsoTranslatedAs
chosen
Indicates that something has an alternative translation or rendering in another language or form.
-
B.
laterTranslatedAs
Indicates that something was translated at a later time into a different language, form, or version under a specified title or expression.
-
C.
languageCommonlyCalled
Indicates that one language is commonly referred to or known by a particular alternative name or label.
-
D.
translatedIn
Indicates that a work, text, or content has been rendered from its original language into another specified language or linguistic form.
-
E.
widelyTranslated
Indicates that a work has been translated into many different languages or versions, reflecting broad international dissemination.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 29, 2026, 7:09 p.m.