Triple
T17100217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Angels |
E414958
|
entity |
| Predicate | communicate |
P40250
|
FINISHED |
| Object | divine messages |
—
|
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: divine messages | Statement: [Holy Angels, communicate, divine messages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicate Context triple: [Holy Angels, communicate, divine messages]
-
A.
communicationPrinciple
Indicates a guiding rule or norm that shapes how communication should be conducted between entities.
-
B.
communicationTrait
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
-
C.
communicationSkill
Indicates the degree to which an entity effectively conveys, receives, and interprets information in interactions with others.
-
D.
communicatesTo
chosen
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
E.
communicationPhilosophy
Indicates the guiding principles or approach an entity uses when communicating with others, such as tone, style, and core beliefs about how communication should occur.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc0182cc8190b8aa9c980f11ba57 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.