Triple
T5646711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ᾍδης |
E124401
|
entity |
| Predicate | receivedDomainAfter |
P60288
|
FINISHED |
| Object | division of the cosmos among Zeus, Poseidon, and Hades |
—
|
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: division of the cosmos among Zeus, Poseidon, and Hades | Statement: [ᾍδης, receivedDomainAfter, division of the cosmos among Zeus, Poseidon, and Hades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedDomainAfter Context triple: [ᾍδης, receivedDomainAfter, division of the cosmos among Zeus, Poseidon, and Hades]
-
A.
laterDomain
chosen
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
B.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified entity.
-
C.
indicatesDomain
Indicates a domain or area of knowledge, activity, or applicability to which something (such as a concept, resource, or entity) belongs or is relevant.
-
D.
recognizedAsDomain
Indicates that one entity is acknowledged or accepted as a valid or authoritative domain associated with another entity.
-
E.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022abf0108190b10b3a9fe1688bf9 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.