Triple
T37912194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elijah Bradley |
E945713
|
entity |
| Predicate | previouslyClaimedPowerSource |
P201505
|
FINISHED |
| Object | grandfather’s blood transfusions |
—
|
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: grandfather’s blood transfusions | Statement: [Elijah Bradley, previouslyClaimedPowerSource, grandfather’s blood transfusions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyClaimedPowerSource Context triple: [Elijah Bradley, previouslyClaimedPowerSource, grandfather’s blood transfusions]
-
A.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
B.
removedPower
Indicates that one entity has taken away or disabled the power, authority, or capability previously held by another entity.
-
C.
usedToClaim
Indicates that something is employed as evidence, justification, or support in making a particular claim.
-
D.
inPowerSince
Indicates the point in time from which an entity has continuously held a position of authority or power.
-
E.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
- F. None of above. chosen
Provenance (4 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69fffbb513c881909063ecf12467f4a6 |
completed | May 10, 2026, 3:29 a.m. |
Created at: May 3, 2026, 4:20 p.m.