Triple
T26580439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRDAP |
E667062
|
entity |
| Predicate | projectTypeFunded |
P76506
|
FINISHED |
| Object | improvements to public outdoor recreation areas |
—
|
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: improvements to public outdoor recreation areas | Statement: [FRDAP, projectTypeFunded, improvements to public outdoor recreation areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectTypeFunded Context triple: [FRDAP, projectTypeFunded, improvements to public outdoor recreation areas]
-
A.
numberOfProjectsFunded
Indicates the quantity of projects that have received funding from a given source or entity.
-
B.
eligibleProjectType
chosen
Indicates that a project belongs to a category or type that qualifies it for a specific program, process, or benefit.
-
C.
funderType
Indicates the category or kind of organization or individual that provides funding in the relationship.
-
D.
fundedEntityType
Indicates the type or category of entity that receives funding in the described funding relationship.
-
E.
publiclyFunded
Indicates that the entity receives financial support from public sources such as government budgets or taxpayer funds.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:02 a.m.