Triple
T27235773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permanent School Fund |
E682266
|
entity |
| Predicate | fundingFor |
P142482
|
FINISHED |
| Object | Texas public school districts |
—
|
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: Texas public school districts | Statement: [Permanent School Fund, fundingFor, Texas public school districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingFor Context triple: [Permanent School Fund, fundingFor, Texas public school districts]
-
A.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
B.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
C.
fundingComponent
Indicates that one entity serves as a financial contributor or funding source for another entity or activity.
-
D.
fundingFocus
Indicates that one entity’s funding is directed toward or prioritized for a particular target, theme, or area of activity.
-
E.
includesFundingFor
chosen
Indicates that one entity’s financial resources or budget allocation explicitly cover or provide funding for another entity, project, or 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 9:47 a.m.