Triple
T25591183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSWE Group |
E641525
|
entity |
| Predicate | providesFinancialBackingTo |
P33009
|
FINISHED |
| Object | Aston Villa FC |
—
|
NE NERFINISHED |
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: Aston Villa FC | Statement: [NSWE Group, providesFinancialBackingTo, Aston Villa FC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesFinancialBackingTo Context triple: [NSWE Group, providesFinancialBackingTo, Aston Villa FC]
-
A.
fundFinancedBy
Indicates that a particular fund receives its financial resources or backing from a specified source or entity.
-
B.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
C.
alsoProvidesFinanceIn
Indicates that an entity, in addition to other roles or services, supplies financial support or funding within a specified context or location.
-
D.
funderOf
chosen
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
E.
grantsCreditFor
Indicates that one entity recognizes or awards academic or other formal credit to another entity for a specific activity, course, or achievement.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 4:24 p.m.