Triple
T7097473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Villans |
E165367
|
entity |
| Predicate | associatedWithSupporters |
P74897
|
FINISHED |
| Object | Aston Villa fans |
—
|
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: Aston Villa fans | Statement: [The Villans, associatedWithSupporters, Aston Villa fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSupporters Context triple: [The Villans, associatedWithSupporters, Aston Villa fans]
-
A.
associatedWithSupportersSong
Indicates that there is a relationship between an entity and a supporters’ song, such as being linked to, represented by, or commonly accompanied by that song.
-
B.
usedBySupporters
Indicates that something is utilized or employed by supporters of a person, group, cause, or entity.
-
C.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
-
D.
sponsorAssociatedWith
Indicates a relationship where a sponsor is connected to, involved with, or responsible for supporting another entity.
-
E.
numberOfSupporters
Indicates the quantity of entities that provide backing, endorsement, or support to a given entity or proposition.
- F. None of above. chosen
Provenance (4 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5561dd08190be6b784754a0c1bc |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:41 p.m.