Triple
T13966255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keos |
E335930
|
entity |
| Predicate | hasAncientNameForm |
P20952
|
FINISHED |
| Object | Κέως |
—
|
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: Κέως | Statement: [Keos, hasAncientNameForm, Κέως]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncientNameForm Context triple: [Keos, hasAncientNameForm, Κέως]
-
A.
ancientNameOf
chosen
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
B.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
C.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
D.
hasHistoricNameVariant
Indicates that an entity has an alternative name that was used in a historical period or past context.
-
E.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e8c9e988190a84c9ca8a78b515f |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.