Triple
T2697412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duat |
E58543
|
entity |
| Predicate | judgmentLocationFor |
P41133
|
FINISHED |
| Object | souls of 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: souls of the dead | Statement: [Duat, judgmentLocationFor, souls of the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgmentLocationFor Context triple: [Duat, judgmentLocationFor, souls of the dead]
-
A.
judgeFrom
Indicates that one entity forms an opinion, evaluation, or conclusion about something based on another specified source, basis, or perspective.
-
B.
defendantLocation
Indicates the place or jurisdiction where the defendant is located or resides in relation to a legal matter.
-
C.
judgeAppointmentBy
Indicates that one entity is appointed to the role of judging or evaluating another entity by a specific authority or process.
-
D.
presidingJudgeFrom
Indicates that a particular judge is serving as the presiding judge in a case, proceeding, or jurisdiction originating from a specified place or institution.
-
E.
judge
Indicates that one entity evaluates, forms an opinion about, or makes a decision regarding another entity or situation.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda322af48190833b8a3c006db236 |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd879bb808190bd2c34de1664c816 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:55 p.m.