Triple
T6163635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salesmanship Club of Dallas |
E137502
|
entity |
| Predicate | usesProceedsFor |
P9389
|
FINISHED |
| Object | youth support programs |
—
|
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: youth support programs | Statement: [Salesmanship Club of Dallas, usesProceedsFor, youth support programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProceedsFor Context triple: [Salesmanship Club of Dallas, usesProceedsFor, youth support programs]
-
A.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
B.
revenueUse
chosen
Indicates how generated revenue is allocated, spent, or applied toward specific purposes or activities.
-
C.
usedInTaxPayments
Indicates that something is employed or applied as part of making or fulfilling tax payments.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d5e8edc8190a7a394ee832bac9f |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.