Triple
T35556829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Lakers vs. Boston Celtics |
E1027520
|
entity |
| Predicate | team1Arena |
P82913
|
FINISHED |
| Object | Crypto.com Arena |
—
|
NE NERFINISHED |
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: Crypto.com Arena | Statement: [Los Angeles Lakers vs. Boston Celtics, team1Arena, Crypto.com Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team1Arena Context triple: [Los Angeles Lakers vs. Boston Celtics, team1Arena, Crypto.com Arena]
-
A.
team2ArenaCity
Indicates the city where the second team’s home arena is located.
-
B.
teamArenaControlled
Indicates that a particular team has control or ownership over a specified arena or battleground.
-
C.
homeArenaTeam
Indicates that a particular team uses a specific arena as its primary home venue for hosting games or events.
-
D.
formerTeamArena
Indicates that an arena was previously used as the home venue for a particular team but is no longer their current arena.
-
E.
hostTeamArena
chosen
Indicates that a particular arena serves as the home venue for a specific team.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.