Triple
T36678975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paso del Norte Health Foundation |
E905622
|
entity |
| Predicate | grantsPrograms |
P24549
|
FINISHED |
| Object | Healthy Eating Active Living |
—
|
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: Healthy Eating Active Living | Statement: [Paso del Norte Health Foundation, grantsPrograms, Healthy Eating Active Living]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsPrograms Context triple: [Paso del Norte Health Foundation, grantsPrograms, Healthy Eating Active Living]
-
A.
grantProgram
Indicates that an entity administers or is associated with a structured grant-based funding program.
-
B.
applicablePrograms
Indicates that certain programs are relevant to, valid for, or can be applied in the context of a given entity or situation.
-
C.
sponsoredPrograms
chosen
Indicates that an entity provides financial or resource support to specific programs or initiatives.
-
D.
inspiredPrograms
Indicates that one entity served as a source of inspiration or influence for the creation or design of another entity’s programs.
-
E.
supportingProgram
Indicates that one program provides assistance, resources, or backing to another program or initiative.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:12 p.m.