Triple
T21000076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russ Chandler Stadium |
E517260
|
entity |
| Predicate | hasScoreboardInOutfield |
P3321
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Russ Chandler Stadium, hasScoreboardInOutfield, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoreboardInOutfield Context triple: [Russ Chandler Stadium, hasScoreboardInOutfield, yes]
-
A.
hasScoreboard
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
-
B.
hasScorekeepersBooth
Indicates that one entity includes, contains, or is equipped with a designated booth or area for scorekeepers.
-
C.
hasScoreboardLocation
chosen
Indicates the spatial or logical position where a scoreboard is placed or associated within a given context.
-
D.
usedOnScoreboards
Indicates that something is employed or displayed specifically on scoreboards.
-
E.
hasTeamSidelines
Indicates that one entity serves as the sidelines or boundary area associated with a particular team in a sports or game context.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc24a6dc8190a6bf81cf1d9590c0 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:52 p.m.