Triple
T19294055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wimbledon F.C. |
E482513
|
entity |
| Predicate | supporterReaction |
P130036
|
FINISHED |
| Object | many fans opposed relocation |
—
|
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: many fans opposed relocation | Statement: [Wimbledon F.C., supporterReaction, many fans opposed relocation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supporterReaction Context triple: [Wimbledon F.C., supporterReaction, many fans opposed relocation]
-
A.
supporterBehavior
chosen
Indicates how a supporter acts toward, engages with, or responds to the entity or cause they are supporting.
-
B.
supporter
Indicates a relationship where one entity backs, advocates for, or provides assistance to another entity, often in an ongoing or affiliative way.
-
C.
supporters
Indicates a relationship where one entity backs, endorses, or actively helps another entity, cause, or position.
-
D.
supporterPosition
Indicates the role, stance, or location that a supporter holds in relation to the entity or issue they support.
-
E.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc84500c81908ac53711335ad2d9 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.