Triple
T10744301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Professional Hockey League |
E253410
|
entity |
| Predicate | hasImportPlayerRule |
P2846
|
FINISHED |
| Object | limits on non‑North American players |
—
|
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: limits on non‑North American players | Statement: [Southern Professional Hockey League, hasImportPlayerRule, limits on non‑North American players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportPlayerRule Context triple: [Southern Professional Hockey League, hasImportPlayerRule, limits on non‑North American players]
-
A.
hadImportPlayerSystem
Indicates that an entity utilized or was governed by a system for managing or handling imported players.
-
B.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
D.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
E.
hasDesignatedPlayerRule
Indicates that a sports league or competition uses a designated player rule allowing certain players to be treated differently for roster or salary purposes.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b6b4b48190bad08500fa963062 |
completed | April 9, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.