Triple
T14139610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gol Sur stand |
E350388
|
entity |
| Predicate | hasHomeSupporterRole |
P3508
|
FINISHED |
| Object | Valencia CF ultras and vocal 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: Valencia CF ultras and vocal fans | Statement: [Gol Sur stand, hasHomeSupporterRole, Valencia CF ultras and vocal fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeSupporterRole Context triple: [Gol Sur stand, hasHomeSupporterRole, Valencia CF ultras and vocal fans]
-
A.
hasSupporter
Indicates that one entity supports, endorses, or backs another entity.
-
B.
hasHomeSupport
Indicates that an entity receives assistance, backing, or favorable conditions from its home environment or local supporters.
-
C.
supportsHomeMatchesOf
Indicates that one entity provides backing, resources, or assistance specifically for the home matches of another entity.
-
D.
hasSupporterGroup
chosen
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
-
E.
usesSupporter
Indicates that one entity makes use of another entity that serves as its supporter, helper, or backing resource in performing an action or fulfilling a role.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6111a36081909beff35c88a56960 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:40 a.m.