Triple
T27605583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Ingram |
E700169
|
entity |
| Predicate | laterClaimed |
P192186
|
FINISHED |
| Object | that his confessions were false |
—
|
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: that his confessions were false | Statement: [Paul Ingram, laterClaimed, that his confessions were false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterClaimed Context triple: [Paul Ingram, laterClaimed, that his confessions were false]
-
A.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
B.
claimsLater
chosen
Indicates that one entity makes a claim or assertion about another entity at a later point in time than some referenced event or claim.
-
C.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
D.
usedToClaim
Indicates that something is employed as evidence, justification, or support in making a particular claim.
-
E.
attemptedClaim
Indicates that an entity made an effort to assert or demand a claim, regardless of whether the claim was ultimately accepted or successful.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 27, 2026, 2:09 p.m.