Triple
T26068828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Series Lacrosse |
E657482
|
entity |
| Predicate | typicalTeamLocation |
P3777
|
FINISHED |
| Object | Ontario, Canada |
—
|
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: Ontario, Canada | Statement: [Major Series Lacrosse, typicalTeamLocation, Ontario, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTeamLocation Context triple: [Major Series Lacrosse, typicalTeamLocation, Ontario, Canada]
-
A.
universityTeamLocation
Indicates the location (such as city, state, or country) associated with a university’s team.
-
B.
teamLocationExample
Indicates that a specific location is provided as an example of where a team is based or operates.
-
C.
draftTeamLocation
Indicates the location associated with a team's draft, such as the city or venue where the drafting event or selection took place.
-
D.
teamLocation
chosen
Indicates that a team is based in, associated with, or operates from a particular geographic location.
-
E.
mostTeamsBasedIn
Indicates that the majority of a group’s teams are primarily located or headquartered in a specified 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 26, 2026, 7:27 p.m.