Triple
T63305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Small Business Innovation Research program |
E1257
|
entity |
| Predicate | phaseIIIFundingType |
P936
|
FINISHED |
| Object | non-SBIR funds |
—
|
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: non-SBIR funds | Statement: [Small Business Innovation Research program, phaseIIIFundingType, non-SBIR funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseIIIFundingType Context triple: [Small Business Innovation Research program, phaseIIIFundingType, non-SBIR funds]
-
A.
fundingModel
Indicates how an entity is financially supported or sustained, such as through specific revenue sources, payment structures, or funding mechanisms.
-
B.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
C.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
D.
typeOfSupport
chosen
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
E.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.