Triple
T24023446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayo Vallecano ultras |
E594886
|
entity |
| Predicate | relationshipToClub |
P102426
|
FINISHED |
| Object | hardcore supporters |
—
|
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: hardcore supporters | Statement: [Rayo Vallecano ultras, relationshipToClub, hardcore supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToClub Context triple: [Rayo Vallecano ultras, relationshipToClub, hardcore supporters]
-
A.
relatedToClub
chosen
Indicates that there is an association or connection between an entity and a club, without specifying the exact nature of that relationship.
-
B.
relationToLeague
Indicates the type or nature of a team's or participant's association with a specific league (e.g., membership, affiliation, or standing).
-
C.
roleInClub
Indicates that an entity holds a specific position or function within a particular club.
-
D.
relationshipToPlayer
Indicates the type of personal or social connection an entity has with the player.
-
E.
associatedClubStatus
Indicates the status or condition of a club as it relates to a particular entity or relationship.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d7680d5c81908d6a670159879236 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:52 p.m.