Triple
T28329818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real Oviedo |
E717509
|
entity |
| Predicate | fanShareIssue |
P164279
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Real Oviedo, fanShareIssue, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanShareIssue Context triple: [Real Oviedo, fanShareIssue, 2012]
-
A.
fanDiscussion
Indicates a discussion or conversation among fans about a shared interest, such as a work, person, or event they follow.
-
B.
fanInvolved
Indicates that a fan actively participates in or is directly involved with a particular event, activity, or interaction.
-
C.
fanBaseSharedWith
Indicates that two entities share a common group of fans or supporters.
-
D.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
E.
fan
Indicates that one entity admires, supports, or is enthusiastically devoted to another entity, typically in a recreational or entertainment context.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f649322d1881909297d1b1c607937d |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 28, 2026, 12:31 a.m.