Triple
T1014882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homeric epics |
E21906
|
entity |
| Predicate | hasModernReceptionIn |
P13270
|
FINISHED |
| Object | translations into many languages |
—
|
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: translations into many languages | Statement: [Homeric epics, hasModernReceptionIn, translations into many languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernReceptionIn Context triple: [Homeric epics, hasModernReceptionIn, translations into many languages]
-
A.
historicalReception
chosen
Indicates how an event, work, or figure was received, interpreted, or evaluated by people and institutions over time.
-
B.
hasModernEditions
Indicates that an original work or text has one or more updated or contemporary published editions.
-
C.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
D.
consideredClassic
Indicates that something is widely regarded or recognized as a classic within a particular field, genre, or context.
-
E.
popularInCentury
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c05060819083c51717874074c8 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.