Triple
T30211191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Μαίναλο |
E768069
|
entity |
| Predicate | έχει_εναλλακτική_μεταγραφή |
P130444
|
FINISHED |
| Object | Mainalo |
—
|
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: Mainalo | Statement: [Μαίναλο, έχει_εναλλακτική_μεταγραφή, Mainalo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: έχει_εναλλακτική_μεταγραφή Context triple: [Μαίναλο, έχει_εναλλακτική_μεταγραφή, Mainalo]
-
A.
έχειΕναλλακτικήΓραφή
chosen
Indicates that one entity serves as an alternative written form or spelling variant of another entity.
-
B.
έχειΜεταγραφή
Indicates that an entity has been transferred or has undergone a transfer (e.g., between organizations, teams, or systems).
-
C.
έχει_ανδριάντα
Indicates that an entity has or is associated with a statue (typically of a person).
-
D.
hasAlternativeToponymy
Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
-
E.
hasAlternativeVocalization
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff185488190a49b208e4ac6cf59 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:32 p.m.