Triple
T9196363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Power |
E220721
|
entity |
| Predicate | allegedlyClaimsAbility |
P32091
|
FINISHED |
| Object | communicate with the dead |
—
|
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: communicate with the dead | Statement: [Joe Power, allegedlyClaimsAbility, communicate with the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedlyClaimsAbility Context triple: [Joe Power, allegedlyClaimsAbility, communicate with the dead]
-
A.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
B.
claimsToBe
chosen
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
C.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
D.
claimedRight
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
-
E.
attributeClaim
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd87d6460819097234b5dd3f749b4 |
completed | April 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.