Triple
T2005485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | March of Dimes |
E43570
|
entity |
| Predicate | hasKeyProgram |
P30089
|
FINISHED |
| Object | research grants |
—
|
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: research grants | Statement: [March of Dimes, hasKeyProgram, research grants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyProgram Context triple: [March of Dimes, hasKeyProgram, research grants]
-
A.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
B.
hasComponentProgram
Indicates that one program includes or is composed of another program as a component or sub-program.
-
C.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
-
D.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
E.
keyProgram
chosen
Indicates that a program or application is designated as a primary, central, or most important one within a given context or system.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb898795481909920c1a4c4d62c2d |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.