Triple
T3301825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Barra KC |
E69351
|
entity |
| Predicate | homeMatchActivity |
P47882
|
FINISHED |
| Object | stands and sings in supporters section |
—
|
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: stands and sings in supporters section | Statement: [La Barra KC, homeMatchActivity, stands and sings in supporters section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeMatchActivity Context triple: [La Barra KC, homeMatchActivity, stands and sings in supporters section]
-
A.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
B.
homeBaseOf
Indicates that a particular place serves as the primary location, headquarters, or main operational base for an entity.
-
C.
homeScore
Indicates the number of points or goals scored by the home team or home participant in a game or match.
-
D.
homeClub
Indicates that a particular club is the primary or hosting club associated with a given event, match, or participant.
-
E.
homeManager
Indicates that one entity manages, oversees, or is responsible for the operations or affairs of another entity’s home or household.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a9450481909f0d630e5593085e |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.