Triple
T32113878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luther Lee Boggs |
E820186
|
entity |
| Predicate | abilityClaim |
P6273
|
FINISHED |
| Object | psychic medium |
—
|
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: psychic medium | Statement: [Luther Lee Boggs, abilityClaim, psychic medium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abilityClaim Context triple: [Luther Lee Boggs, abilityClaim, psychic medium]
-
A.
typeOfClaim
chosen
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
B.
modalClaim
Indicates that the statement is being made with a modal qualification, such as possibility, necessity, or obligation, rather than as an unqualified factual claim.
-
C.
causeOfClaim
Indicates the underlying reason, event, or condition that gives rise to a particular claim.
-
D.
claimsEffect
Indicates that one entity asserts or states that another entity has a particular effect or impact.
-
E.
claimProcess
Indicates the process by which a claim (such as an insurance or service claim) is received, evaluated, and resolved between involved parties.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b906a92c819096335394dd7f767e |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.