Triple
T5009105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiresias |
E112569
|
entity |
| Predicate | underworldRole |
P2319
|
FINISHED |
| Object | prophet among the dead |
—
|
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: prophet among the dead | Statement: [Tiresias, underworldRole, prophet among the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underworldRole Context triple: [Tiresias, underworldRole, prophet among the dead]
-
A.
roleInTheology
chosen
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
B.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
C.
necropolisRole
Indicates that an entity has a specific functional or social role in relation to a necropolis (a large cemetery or burial ground).
-
D.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
E.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.