Triple
T31504885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Viernes |
E803789
|
entity |
| Predicate | usesReferees |
P128835
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Super Viernes, usesReferees, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReferees Context triple: [Super Viernes, usesReferees, yes]
-
A.
hasReferees
chosen
Indicates that an entity is associated with one or more referees who oversee, judge, or validate its activities or events.
-
B.
hasRefereesFrom
Indicates that an entity is officiated or overseen by referees originating from a specified source or location.
-
C.
hasProfessionalReferees
Indicates that an entity is associated with one or more individuals who serve as its professional references or referees.
-
D.
overseesReferees
Indicates that one entity has responsibility for supervising, managing, or directing the work and performance of referees.
-
E.
refereesInCompetition
Indicates that an entity serves as a referee or official within a particular competition or event.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 30, 2026, 9:46 p.m.