Triple
T25860347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suda |
E651460
|
entity |
| Predicate | SudaOnLineURL |
P159358
|
FINISHED |
| Object | https://www.cs.uky.edu/~raphael/sol/ |
—
|
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: https://www.cs.uky.edu/~raphael/sol/ | Statement: [Suda, SudaOnLineURL, https://www.cs.uky.edu/~raphael/sol/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SudaOnLineURL Context triple: [Suda, SudaOnLineURL, https://www.cs.uky.edu/~raphael/sol/]
-
A.
meaningInGreek
Indicates that something is expressed, translated, or holds a particular meaning in the Greek language.
-
B.
hasNameInGreek
Indicates that an entity is associated with a specific representation of its name in the Greek language.
-
C.
IPAValueModernGreek
Indicates the modern Greek IPA (International Phonetic Alphabet) pronunciation value associated with a given linguistic unit.
-
D.
hasGreekCounterpart
Indicates that one entity has a corresponding or equivalent counterpart in Greek context, such as in Greek mythology, culture, or language.
-
E.
successorNameInGreekService
Indicates that the predicate specifies the name of a successor as used or rendered in a Greek-language service or context.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6026b467c8190a1f8be336f8679da |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 8:05 a.m.