Triple
T17556892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Re |
E427611
|
entity |
| Predicate | underworldJourney |
P127914
|
FINISHED |
| Object | travels through Duat at night |
—
|
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: travels through Duat at night | Statement: [Re, underworldJourney, travels through Duat at night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underworldJourney Context triple: [Re, underworldJourney, travels through Duat at night]
-
A.
underworldRegion
Indicates a region that is located within or associated with the underworld or subterranean realm.
-
B.
crossToUnderworldBy
Indicates a relationship where an entity travels or passes from the world of the living into the underworld by means of, or with the help of, a specified agent, method, or pathway.
-
C.
positionInUnderworld
Indicates a hierarchical or role-based position that an entity holds within an underworld or criminal organization.
-
D.
underworldRegionJudged
Indicates that a particular region of the underworld is the one in which a judgment or evaluation takes place.
-
E.
undergroundZone
Indicates that something is located in, associated with, or occurring within an area beneath the ground surface.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562357b48190bde6f49df0c983c2 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.