Triple
T28141783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Mustangs football team |
E714360
|
entity |
| Predicate | representedInstitutionLocation |
P58210
|
FINISHED |
| Object | London, Ontario |
—
|
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: London, Ontario | Statement: [Western Mustangs football team, representedInstitutionLocation, London, Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedInstitutionLocation Context triple: [Western Mustangs football team, representedInstitutionLocation, London, Ontario]
-
A.
locatedAtInstitution
Indicates that an entity is situated at, based in, or physically present within a particular institution.
-
B.
memberInstitutionLocation
Indicates that a member institution is located in, or associated with, a specific geographic place or address.
-
C.
locatedInInstitutionType
Indicates that one entity is situated within, or belongs to, an institution of a specified type.
-
D.
originalInstitutionLocation
Indicates the geographic location where an institution was originally founded or first established.
-
E.
homeInstitutionLocation
chosen
Indicates the geographic place where an entity’s primary or home institution is located.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 27, 2026, 9:53 p.m.