Triple
T5791845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Hockey League |
E128411
|
entity |
| Predicate | maximumOveragePlayersPerTeam |
P23145
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Ontario Hockey League, maximumOveragePlayersPerTeam, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumOveragePlayersPerTeam Context triple: [Ontario Hockey League, maximumOveragePlayersPerTeam, 3]
-
A.
teamRosterLimit
Indicates the maximum number of members that are allowed to be on a team’s roster.
-
B.
allowsOveragePlayers
chosen
Indicates that a context, rule, or system permits participation or inclusion of players who exceed a specified age limit.
-
C.
foreignPlayerRosterLimit
Indicates a restriction on how many foreign or non-local players may be included on a team’s roster.
-
D.
maximumScoringRunnersPerTeam
Indicates the maximum number of runners on a team who can be counted or considered based on their scoring performance.
-
E.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a5870b88190bbfaac2782635128 |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.