Triple
T29866726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blender Development Fund |
E758480
|
entity |
| Predicate | acceptsContributionFrom |
P79923
|
FINISHED |
| Object | individuals |
—
|
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: individuals | Statement: [Blender Development Fund, acceptsContributionFrom, individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsContributionFrom Context triple: [Blender Development Fund, acceptsContributionFrom, individuals]
-
A.
acceptsContributions
chosen
Indicates that an entity receives or allows contributions (such as funds, content, or resources) from other entities.
-
B.
hasContributionFrom
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
C.
tributeFrom
Indicates that one entity pays or provides tribute, often as a sign of submission or obligation, to another entity.
-
D.
tributeTo
Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward another entity.
-
E.
participantMayAlsoContributeTo
Indicates that an entity participating in something is additionally allowed or able to contribute to it in some way.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67689a3908190bdef1a1108f42f87 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:51 p.m.