Triple
T30148199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celebrity Poker Showdown |
E766312
|
entity |
| Predicate | hasCharityAngle |
P105120
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Celebrity Poker Showdown, hasCharityAngle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharityAngle Context triple: [Celebrity Poker Showdown, hasCharityAngle, true]
-
A.
hasCharitySingle
Indicates that an entity is associated with exactly one specific charitable organization or charitable initiative.
-
B.
hasCharitableComponent
chosen
Indicates that something includes or is associated with a charitable element, such as donations, philanthropy, or support for a charitable cause.
-
C.
hasCharityConnection
Indicates a relationship in which one entity is connected to another through charitable activities, support, or affiliation.
-
D.
isCharity
Indicates that an entity operates as a charitable organization or is recognized as a charity.
-
E.
hasCharitableFunction
Indicates that an entity performs or is designated to perform activities intended for charitable purposes or public benefit.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 29, 2026, 7:19 p.m.