Triple
T35418572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunedin Stadium |
E1023715
|
entity |
| Predicate | isTrainingSiteOf |
P62959
|
FINISHED |
| Object | Toronto Blue Jays |
—
|
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: Toronto Blue Jays | Statement: [Dunedin Stadium, isTrainingSiteOf, Toronto Blue Jays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTrainingSiteOf Context triple: [Dunedin Stadium, isTrainingSiteOf, Toronto Blue Jays]
-
A.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
B.
isTypeSiteOf
Indicates that a site serves as the specific location or setting where a particular type, category, or classification is realized or occurs.
-
C.
servesAsTeachingSiteFor
chosen
Indicates that one entity functions as a location or institution where teaching, training, or educational activities are conducted for another entity.
-
D.
isSatelliteSiteOf
Indicates that one site functions as a subsidiary, dependent, or secondary location associated with another primary or main site.
-
E.
isKeySiteOf
Indicates that a location serves as an important or central place for a particular event, activity, process, or function.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:03 p.m.