Triple
T1461403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Pope |
E31518
|
entity |
| Predicate | translatedFromLanguage |
P20095
|
FINISHED |
| Object | Ancient Greek |
—
|
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: Ancient Greek | Statement: [Alexander Pope, translatedFromLanguage, Ancient Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translatedFromLanguage Context triple: [Alexander Pope, translatedFromLanguage, Ancient Greek]
-
A.
translationTargetLanguage
Indicates the language into which content is being or has been translated.
-
B.
otherLanguage
Indicates that an entity has or uses an additional language distinct from its primary or main language.
-
C.
translationDirection
chosen
Indicates the source and target languages involved in a translation, specifying the direction from the original language to the translated language.
-
D.
translator
Indicates that one entity serves to convert or render content from one language or form into another for a second entity.
-
E.
translationApproximate
Indicates that one entity is an inexact or approximate translation of another, preserving general meaning but not precise wording or full detail.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59ecb60819082217b034e18381f |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.