Triple
T972167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Prince’s Trust |
E20967
|
entity |
| Predicate | charityNumber |
P22705
|
FINISHED |
| Object | 1079675 |
—
|
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: 1079675 | Statement: [The Prince’s Trust, charityNumber, 1079675]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charityNumber Context triple: [The Prince’s Trust, charityNumber, 1079675]
-
A.
associatedCharity
Indicates that one entity has a formal or recognized charitable affiliation or partnership with another entity.
-
B.
charityComponent
Indicates that one entity functions as a charitable element, feature, or part within another entity or larger arrangement.
-
C.
hasCharitySingle
Indicates that an entity is associated with exactly one specific charitable organization or charitable initiative.
-
D.
hasCharitableFoundation
Indicates that an entity maintains or is associated with a charitable foundation, typically for philanthropic or nonprofit activities.
-
E.
philanthropicBeneficiary
Indicates that one entity is the recipient or target of another entity’s philanthropic giving or charitable support.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b44c38f08190997e141d424e9e04 |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a6aa2c8190aebba71320ab678f |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b38630848190bd3898a4f42018ad |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.