Triple
T34102206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John 8:12 |
E874602
|
entity |
| Predicate | keyGreekTerm |
P178234
|
FINISHED |
| Object | phōs (light) |
—
|
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: phōs (light) | Statement: [John 8:12, keyGreekTerm, phōs (light)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyGreekTerm Context triple: [John 8:12, keyGreekTerm, phōs (light)]
-
A.
meaningInGreek
Indicates that something is expressed, translated, or holds a particular meaning in the Greek language.
-
B.
SudaOnLineURL
Indicates that an entity has an associated online URL entry in the Suda (Suda On Line) digital resource.
-
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.
hasNameInGreek
Indicates that an entity is associated with a specific representation of its name in the Greek language.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c6bceb081909bbc2f65c0fe036c |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:53 a.m.