Triple
T23673644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Κωκυτός |
E584804
|
entity |
| Predicate | hasCounterpartName |
P152931
|
FINISHED |
| Object | Cocytus in Latin sources |
—
|
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: Cocytus in Latin sources | Statement: [Κωκυτός, hasCounterpartName, Cocytus in Latin sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCounterpartName Context triple: [Κωκυτός, hasCounterpartName, Cocytus in Latin sources]
-
A.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
B.
hasCounterpartNameLanguage
Indicates that an entity’s counterpart (e.g., in another context or system) has a name expressed in a specified language.
-
C.
hasCounterpartNickname
Indicates that one entity is used as an alternative or counterpart nickname for another entity.
-
D.
counterpartEnglishName
Indicates that an entity has a corresponding counterpart whose name is given in English.
-
E.
hasSmallerCounterpart
Indicates that one entity has another entity as its corresponding version that is smaller in size, scale, or magnitude.
- F. None of above. chosen
Provenance (4 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f1dee08190bfe78564c65f01ad |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:51 p.m.