Triple
T24697128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germantown Charity Horse Show |
E611621
|
entity |
| Predicate | fundraisingTarget |
P36498
|
FINISHED |
| Object | local charitable organizations |
—
|
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: local charitable organizations | Statement: [Germantown Charity Horse Show, fundraisingTarget, local charitable organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundraisingTarget Context triple: [Germantown Charity Horse Show, fundraisingTarget, local charitable organizations]
-
A.
raisedMoneyFor
Indicates that one entity collected or obtained funds specifically to support or benefit another entity, cause, or purpose.
-
B.
approximateFundsRaised
Indicates an estimated amount of money that has been raised, rather than an exact or final total.
-
C.
philanthropicGoal
Indicates a relationship where an action, initiative, or entity is directed toward achieving a charitable or socially beneficial objective.
-
D.
fundingObjective
chosen
Indicates the purpose or goal for which financial resources are being sought, allocated, or used.
-
E.
crowdfundingGoalMet
Indicates that the funding target for a crowdfunding campaign has been reached or exceeded.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:22 a.m.