Triple
T37505062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curveball |
E932068
|
entity |
| Predicate | claimsLater |
P192186
|
FINISHED |
| Object | discredited |
—
|
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: discredited | Statement: [Curveball, claimsLater, discredited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsLater Context triple: [Curveball, claimsLater, discredited]
-
A.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
-
B.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
C.
claimThrough
Indicates that one entity asserts ownership, right, or entitlement to another entity by means of, or via the mediation of, a specified intermediary or channel.
-
D.
claimsToMark
Indicates that one entity asserts or alleges that it has marked, labeled, or designated another entity in some specified way.
-
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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.