Triple
T35832846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Dogs |
E1035844
|
entity |
| Predicate | playsDivision |
P11735
|
FINISHED |
| Object | QMJHL Maritimes Division |
—
|
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: QMJHL Maritimes Division | Statement: [Sea Dogs, playsDivision, QMJHL Maritimes Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsDivision Context triple: [Sea Dogs, playsDivision, QMJHL Maritimes Division]
-
A.
gameDivision
Indicates a hierarchical or categorical separation of a game into distinct parts, sections, or groups.
-
B.
divisionalPlay
Indicates that the related entities are competing or interacting within the same division of a larger league or organizational structure.
-
C.
teamDivision
Indicates how a larger team is split into smaller subgroups or units for organization or collaboration.
-
D.
competesInDivision
chosen
Indicates that an entity participates in competitive activities within a specified division or tier of a larger organizational or league structure.
-
E.
featuredDivision
Indicates that one division is highlighted or given special prominence in relation to others within a particular context.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.