Triple
T7830943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elite Ice Hockey League |
E181364
|
entity |
| Predicate | allowsNonUKPlayers |
P21278
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Elite Ice Hockey League, allowsNonUKPlayers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsNonUKPlayers Context triple: [Elite Ice Hockey League, allowsNonUKPlayers, yes]
-
A.
allowsForeignPlayers
chosen
Indicates that an entity permits participation or involvement by players who are from foreign countries or outside its primary jurisdiction.
-
B.
allowsNonFootballMembers
Indicates that an entity permits individuals or groups who are not part of a football organization or team to be members.
-
C.
allowsOveragePlayers
Indicates that a context, rule, or system permits participation or inclusion of players who exceed a specified age limit.
-
D.
canLoanPlayersTo
Indicates that one entity has the authority or ability to temporarily transfer its players to another entity.
-
E.
playsInternationalMatchesIn
Indicates that an athlete or team participates in international matches held in a specified location or competition 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb0647848081908d74e09f52d0919e |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:44 p.m.