Triple
T28198176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Have You Ever |
E716501
|
entity |
| Predicate | isCharitySingleFor |
P133962
|
FINISHED |
| Object | Children in Need |
—
|
NE NERFINISHED |
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: Children in Need | Statement: [Have You Ever, isCharitySingleFor, Children in Need]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCharitySingleFor Context triple: [Have You Ever, isCharitySingleFor, Children in Need]
-
A.
isCharitySingle
Indicates that a charity operates independently and is not part of a group, network, or multi-entity structure.
-
B.
hasCharitySingle
Indicates that an entity is associated with exactly one specific charitable organization or charitable initiative.
-
C.
isCharity
Indicates that an entity operates as a charitable organization or is recognized as a charity.
-
D.
usedAsCharitySingle
chosen
Indicates that something is used as a standalone charitable item or release, typically for the purpose of raising funds or awareness for charity.
-
E.
charitySinglePurpose
Indicates that a charity is established and operated for a single, specific charitable purpose rather than multiple distinct purposes.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f642d34ab881908f05b9c26314c8e8 |
completed | May 2, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:29 p.m.