Triple
T17276384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lux aeterna |
E419401
|
entity |
| Predicate | addressedFor |
P126591
|
FINISHED |
| Object | souls in purgatory |
—
|
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 in purgatory | Statement: [Lux aeterna, addressedFor, souls in purgatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressedFor Context triple: [Lux aeterna, addressedFor, souls in purgatory]
-
A.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
B.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
-
C.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
D.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
E.
addressing
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332625c48190a25bf51543d797c3 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3874077948190acf5706cfe917d29 |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:40 a.m.