Triple
T33357752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clothes Off Our Back Foundation |
E854121
|
entity |
| Predicate | raisesMoneyThrough |
P170974
|
FINISHED |
| Object | online auctions |
—
|
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: online auctions | Statement: [Clothes Off Our Back Foundation, raisesMoneyThrough, online auctions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisesMoneyThrough Context triple: [Clothes Off Our Back Foundation, raisesMoneyThrough, online auctions]
-
A.
raisedMoneyFor
Indicates that one entity collected or obtained funds specifically to support or benefit another entity, cause, or purpose.
-
B.
seeksFundingFrom
Indicates that one entity is actively trying to obtain financial support or investment from another entity.
-
C.
capitalRaisingMethod
chosen
Indicates the method or mechanism by which an entity raises capital or obtains funding.
-
D.
owedMoneyTo
Indicates that one entity has a financial obligation or debt that must be paid to another entity.
-
E.
raisesCapitalFrom
Indicates that one entity obtains funding or financial resources from another entity.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.