Triple
T5452456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100&Change competition |
E122399
|
entity |
| Predicate | grantPurpose |
P18220
|
FINISHED |
| Object | implementation of a solution |
—
|
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: implementation of a solution | Statement: [100&Change competition, grantPurpose, implementation of a solution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantPurpose Context triple: [100&Change competition, grantPurpose, implementation of a solution]
-
A.
additionalFundingPurpose
Indicates the specific reason or intended use for which additional funding is sought or allocated beyond the original amount.
-
B.
reasonForGrant
chosen
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
-
C.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
D.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
E.
grantProgram
Indicates that an entity administers or is associated with a structured grant-based funding program.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.