Triple
T11056092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Adicción |
E261379
|
entity |
| Predicate | homeEndInStadium |
P97546
|
FINISHED |
| Object | stands behind the goal |
—
|
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 behind the goal | Statement: [La Adicción, homeEndInStadium, stands behind the goal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeEndInStadium Context triple: [La Adicción, homeEndInStadium, stands behind the goal]
-
A.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
B.
homeStadiumFeatureOf
Indicates that a stadium serves as the designated home venue or primary hosting facility for a particular team, club, or organization.
-
C.
homeStadiumNote
Indicates that there is an explanatory note or qualification about the home stadium relationship between a team and its stadium.
-
D.
homeStadiumFeature
Indicates that a specified feature or characteristic is present in, or associated with, a team's home stadium.
-
E.
homeStadiumUse
Indicates that a particular stadium is used as the home venue by a specific team 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a152b4819095b74a8996346077 |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.