Triple
T16887743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rynearson Stadium |
E421581
|
entity |
| Predicate | hasSidelines |
P38457
|
FINISHED |
| Object | home sideline on west side |
—
|
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: home sideline on west side | Statement: [Rynearson Stadium, hasSidelines, home sideline on west side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSidelines Context triple: [Rynearson Stadium, hasSidelines, home sideline on west side]
-
A.
hasHomeTeamSideline
chosen
Indicates that a particular sideline is designated as belonging to or used by the home team in a sporting event or venue.
-
B.
hasCitySide
Indicates that one entity is located on or corresponds to a particular side or area of a city relative to another entity.
-
C.
hasCountrySide
Indicates that something is located on, borders, or is associated with the side or boundary of a specified country.
-
D.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
E.
hasBside
Indicates that one item serves as the B-side counterpart or secondary track associated with another primary item, typically in a recording or media release.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc1f42481909dcf595358c23497 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.