Triple
T29986884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE section |
E761755
|
entity |
| Predicate | hasFundingFrom |
P67
|
FINISHED |
| Object | IEEE member dues allocation |
—
|
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: IEEE member dues allocation | Statement: [IEEE section, hasFundingFrom, IEEE member dues allocation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFundingFrom Context triple: [IEEE section, hasFundingFrom, IEEE member dues allocation]
-
A.
fundedBy
chosen
Indicates that an entity receives financial support or resources from another entity.
-
B.
funderOf
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
C.
fundFinancedBy
Indicates that a particular fund receives its financial resources or backing from a specified source or entity.
-
D.
seeksFundingFrom
Indicates that one entity is actively trying to obtain financial support or investment from another entity.
-
E.
permittedFundingFrom
Indicates that providing financial resources from one entity to another is allowed under specified rules or conditions.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 6:36 p.m.