Triple
T5221658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Patch Boys |
E117882
|
entity |
| Predicate | homeMatchesSection |
P42101
|
FINISHED |
| Object | south stand at BMO 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: south stand at BMO Field | Statement: [Red Patch Boys, homeMatchesSection, south stand at BMO Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeMatchesSection Context triple: [Red Patch Boys, homeMatchesSection, south stand at BMO Field]
-
A.
homeSection
Indicates that something belongs to, is part of, or is designated as the primary/home section within a larger structure or collection.
-
B.
homeMatchActivity
Indicates an activity or event that takes place during a match played at the home venue of a team or participant.
-
C.
homeSectionName
Indicates the designated name or label assigned to a particular section of a home or homepage.
-
D.
homeStadiumSection
chosen
Indicates that a particular stadium section serves as the designated home area for a specific team or entity.
-
E.
homeStadiumFeatureOf
Indicates that a stadium serves as the designated home venue or primary hosting facility for a particular team, club, or organization.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7aba05b48190b6a7fc52ab3532f0 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.