Triple
T32259728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian O'Blivion |
E824117
|
entity |
| Predicate | religiousLikeRole |
P143890
|
FINISHED |
| Object | media prophet |
—
|
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: media prophet | Statement: [Brian O'Blivion, religiousLikeRole, media prophet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousLikeRole Context triple: [Brian O'Blivion, religiousLikeRole, media prophet]
-
A.
religiousOrientationRole
Indicates a role or position that an entity holds in relation to a particular religious orientation or affiliation.
-
B.
religiousTextRole
Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
-
C.
religiousThemeRole
Indicates that an entity plays a specific role or function within a religious theme or context.
-
D.
religiousAndSpiritualRole
chosen
Indicates that an entity holds or fulfills a religious or spiritual function, office, or responsibility in relation to another entity or context.
-
E.
regionReligiousRole
Indicates the role or function that religion plays within a particular region, such as its religious status, significance, or designated religious purpose.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 1, 2026, 12:41 a.m.