Triple
T37569227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pretos Velhos |
E934641
|
entity |
| Predicate | communicateThrough |
P59911
|
FINISHED |
| Object | spirit mediums |
—
|
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: spirit mediums | Statement: [Pretos Velhos, communicateThrough, spirit mediums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicateThrough Context triple: [Pretos Velhos, communicateThrough, spirit mediums]
-
A.
communicatesTo
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
B.
communicatesFrom
Indicates that information, messages, or signals are sent or expressed from one entity to another.
-
C.
usedToCommunicate
chosen
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
D.
designedToCommunicate
Indicates that something has been intentionally created or configured for the purpose of conveying information or messages to others.
-
E.
enablesCommunicationWith
Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.