Triple
T23899479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parc Jarry tennis stadium |
E600999
|
entity |
| Predicate | associatedWithCityEvent |
P125128
|
FINISHED |
| Object | Montreal summer tennis tournament |
—
|
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: Montreal summer tennis tournament | Statement: [Parc Jarry tennis stadium, associatedWithCityEvent, Montreal summer tennis tournament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCityEvent Context triple: [Parc Jarry tennis stadium, associatedWithCityEvent, Montreal summer tennis tournament]
-
A.
associatedCityEvent
Indicates a relationship where a city is linked to, involved in, or serves as the location for a particular event.
-
B.
associatedWithCorporateEvent
Indicates that an entity has a connection or involvement with a specific corporate event.
-
C.
associatedWithEventHost
Indicates that an entity has a relationship or connection with the host of a particular event.
-
D.
associatedWithCitySports
chosen
Indicates a relationship where an entity has a connection or involvement with city-level sports activities, organizations, or events.
-
E.
mainEventCity
Indicates the city in which the primary or main event 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddca9708190acd3e9edc9b5940b |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.