Triple
T11197620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pericos |
E264961
|
entity |
| Predicate | fanIdentityOf |
P897
|
FINISHED |
| Object | RCD Espanyol 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: RCD Espanyol supporters | Statement: [Pericos, fanIdentityOf, RCD Espanyol supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanIdentityOf Context triple: [Pericos, fanIdentityOf, RCD Espanyol supporters]
-
A.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
B.
fanOfSport
Indicates that a person supports, follows, or has a strong interest in a particular sport.
-
C.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
D.
fanBase
chosen
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
E.
fanbaseCharacteristic
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c082fc8190866c574f698b59ef |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.