Triple
T34910338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1989 Wales Conference Finals |
E1006845
|
entity |
| Predicate | locationTeam1HomeGames |
P61399
|
FINISHED |
| Object | Montreal Forum |
E22217
|
NE 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: Montreal Forum | Statement: [1989 Wales Conference Finals, locationTeam1HomeGames, Montreal Forum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationTeam1HomeGames Context triple: [1989 Wales Conference Finals, locationTeam1HomeGames, Montreal Forum]
-
A.
locationTeam1Home
chosen
Indicates that the specified location serves as the home venue or home ground for team 1 in the relationship.
-
B.
locationTeam2Home
Indicates that the specified location serves as the home venue or home ground for the second team involved in the context.
-
C.
pointsHomeTeam
Indicates the number of points scored or accumulated by the home team in a game or match.
-
D.
hostCityTeam2HomeGames
Indicates that a city serves as the home location where Team 2 plays its home games.
-
E.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
- F. None of above.
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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8af720c8190981ab486e02ef874 |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.