Triple
T34537354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Hermes |
E886705
|
entity |
| Predicate | greekIdentificationOfDeity |
P111278
|
FINISHED |
| Object | Thoth with Hermes |
—
|
NE NERFINISHED |
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: Thoth with Hermes | Statement: [City of Hermes, greekIdentificationOfDeity, Thoth with Hermes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: greekIdentificationOfDeity Context triple: [City of Hermes, greekIdentificationOfDeity, Thoth with Hermes]
-
A.
deityIdentification
Indicates that one entity is identified, recognized, or designated as a deity in relation to another entity or context.
-
B.
equivalentInGreekReligion
chosen
Indicates that two religious figures, concepts, or practices are counterparts or direct analogues of each other within the context of Greek religion.
-
C.
typeOfGreek
Indicates that one entity is a specific kind or category of Greek associated with the other entity.
-
D.
equivalentInRomanMythology
Indicates that one entity corresponds to or is identified as the Roman-mythology counterpart of another entity from a different mythological tradition.
-
E.
recognizedAsGreekBy
Indicates that one entity is regarded or acknowledged as Greek by another entity.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71feeedc081908468bf1e2e2ef3e0 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.