Triple
T10416318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Deltas |
E245523
|
entity |
| Predicate | usedCrowdfundingInFinancing |
P38335
|
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: [San Francisco Deltas, usedCrowdfundingInFinancing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCrowdfundingInFinancing Context triple: [San Francisco Deltas, usedCrowdfundingInFinancing, true]
-
A.
usedOnlineFundraising
chosen
Indicates that an entity has engaged in raising money via internet-based fundraising platforms or campaigns.
-
B.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
C.
seeksFundingFrom
Indicates that one entity is actively trying to obtain financial support or investment from another entity.
-
D.
usesFundraisingMethod
Indicates that one entity employs or applies a particular fundraising method as its means of raising funds.
-
E.
fundingFocus
Indicates that one entity’s funding is directed toward or prioritized for a particular target, theme, or area of activity.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea108fec8190819423630888fa2b |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.