Triple
T34997004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 NBA D-League Championship |
E1009563
|
entity |
| Predicate | hostTeamForGame1 |
P61036
|
FINISHED |
| Object | Santa Cruz Warriors |
—
|
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: Santa Cruz Warriors | Statement: [2013 NBA D-League Championship, hostTeamForGame1, Santa Cruz Warriors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostTeamForGame1 Context triple: [2013 NBA D-League Championship, hostTeamForGame1, Santa Cruz Warriors]
-
A.
hostTeam
Indicates that one team serves as the host (home) team in relation to a particular game, match, or event.
-
B.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
C.
firstNightGameHomeTeam
chosen
Indicates that the specified team is the home team in the first night game of a given series, season, or event.
-
D.
homeTeamForGame5
Indicates which team is designated as the home team in game 5 of a series or schedule.
-
E.
locationTeam1Home
Indicates that the specified location serves as the home venue or home ground for team 1 in the relationship.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.