Triple
T32095265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powers of the World |
E819707
|
entity |
| Predicate | hasTypeOfAddressee |
P379
|
FINISHED |
| Object | reverential |
—
|
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: reverential | Statement: [Powers of the World, hasTypeOfAddressee, reverential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfAddressee Context triple: [Powers of the World, hasTypeOfAddressee, reverential]
-
A.
addresseeType
Indicates the role or category of the entity that is the intended recipient or target of a communication or message.
-
B.
hasTypeOfRecipient
chosen
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
-
C.
hasAddressRole
Indicates that a specific role or function is associated with an address within a given context (e.g., billing, shipping, primary).
-
D.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
E.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 1, 2026, 12:25 a.m.