Triple
T413091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-Mobile Park |
E9532
|
entity |
| Predicate | scoreboardLocation |
P3321
|
FINISHED |
| Object | left field |
—
|
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: left field | Statement: [T-Mobile Park, scoreboardLocation, left field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreboardLocation Context triple: [T-Mobile Park, scoreboardLocation, left field]
-
A.
hasScoreboardLocation
chosen
Indicates the spatial or logical position where a scoreboard is placed or associated within a given context.
-
B.
hasScoreboard
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
-
C.
game2Location
Indicates that a game takes place at, or is associated with, a specific location.
-
D.
arenaLocation
Indicates that an arena is located at or within a specified place or geographic location.
-
E.
game4Location
Indicates the place or venue where the fourth game in a series or sequence takes place.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecdc422881908910428fd1aee7c6 |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e9749234819084b0ce94faabd0b1 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.