Triple
T11849344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moncton Wildcats |
E281866
|
entity |
| Predicate | homeProvinceLeagueRegion |
P44797
|
FINISHED |
| Object | Maritimes region of QMJHL |
—
|
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: Maritimes region of QMJHL | Statement: [Moncton Wildcats, homeProvinceLeagueRegion, Maritimes region of QMJHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeProvinceLeagueRegion Context triple: [Moncton Wildcats, homeProvinceLeagueRegion, Maritimes region of QMJHL]
-
A.
homeRegionLeague
Indicates that a league is the primary or native regional competition associated with an entity (such as a team or club).
-
B.
teamProvinceOrState
chosen
Indicates that a team is located in, or associated with, a particular province or state.
-
C.
baseProvince
Indicates that one administrative or territorial unit serves as the primary or originating province associated with another entity.
-
D.
playsForProvinceOrState
Indicates that an athlete or player is a member of, or represents, a particular provincial or state-level team or organization.
-
E.
homeCityRegion
Indicates the city or broader regional area that serves as an entity’s primary place of residence or origin.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65db52c8190a218736da17d0153 |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.