Triple
T17612238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Γέεννα |
E428990
|
entity |
| Predicate | σχετίζεταιΓεωγραφικάΜε |
P3227
|
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: [Γέεννα, σχετίζεταιΓεωγραφικάΜε, Κοιλάδα του Εννόμ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: σχετίζεταιΓεωγραφικάΜε Context triple: [Γέεννα, σχετίζεταιΓεωγραφικάΜε, Κοιλάδα του Εννόμ]
-
A.
typicalGeographicalAssociation
Indicates a usual or characteristic geographical connection between entities, such as a place commonly associated with a person, group, or phenomenon.
-
B.
συνδέεταιΜεΠεδιάδα
Indicates a relationship where something is connected or linked to a plain (flat land area).
-
C.
geographicContext
chosen
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
D.
associatedTopography
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
-
E.
impliesGeographicalFact
Indicates that one geographical statement or condition logically entails the truth of another geographical fact.
- 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_69e46d2dfa688190a0b9b396bb6133cc |
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.