Triple
T8106387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La 12 |
E189236
|
entity |
| Predicate | notableRivalSupportersGroupOf |
P80483
|
FINISHED |
| Object | River Plate 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: River Plate supporters | Statement: [La 12, notableRivalSupportersGroupOf, River Plate supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRivalSupportersGroupOf Context triple: [La 12, notableRivalSupportersGroupOf, River Plate supporters]
-
A.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
-
B.
supporterGroupNickname
Indicates that a particular nickname is used to refer to a group of supporters associated with an entity.
-
C.
notableTeams
Indicates that there is a noteworthy association between an entity and one or more teams with which it is significantly connected or recognized.
-
D.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
-
E.
notableClub
Indicates that an entity is prominently associated with or recognized for membership in a particular club or organization.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42f735c8819090d0d822644c0a51 |
completed | March 31, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69cb04a2ed1c8190b73562321ad688bc |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:31 p.m.