Triple
T17612268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Γέεννα |
E428990
|
entity |
| Predicate | αντιστοιχείΣε |
P106119
|
FINISHED |
| Object | λατινικός όρος gehenna |
—
|
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: λατινικός όρος gehenna | Statement: [Γέεννα, αντιστοιχείΣε, λατινικός όρος gehenna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: αντιστοιχείΣε Context triple: [Γέεννα, αντιστοιχείΣε, λατινικός όρος gehenna]
-
A.
correspondsWith
chosen
Indicates that two entities are in mutual alignment or agreement, such that one matches, parallels, or is equivalent to the other in a specified respect.
-
B.
εκβάλλειΚοντάΣε
Indicates that one entity discharges, empties, or flows out in close proximity to another entity.
-
C.
έχει_ανδριάντα
Indicates that an entity has or is associated with a statue (typically of a person).
-
D.
τιμάται_ως
Indicates that one entity is honored, revered, or regarded with special esteem in the capacity or role specified by another entity.
-
E.
εκβάλλειΣτο
Indicates that one geographical feature (typically a river or stream) flows into and empties into another body of water.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2eaa348190a8226eef8c0d6e31 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.