Triple
T424351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECHL |
E8172
|
entity |
| Predicate | allowsAHLAssignments |
P13612
|
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: [ECHL, allowsAHLAssignments, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsAHLAssignments Context triple: [ECHL, allowsAHLAssignments, yes]
-
A.
NHLaffiliate
Indicates that one entity serves as a National Hockey League (NHL) affiliate or farm team relationship to another, typically linking a minor-league team to its parent NHL club.
-
B.
allowedNBAPlayersFrom
Indicates that certain NBA players are permitted or eligible to come from a specified source, such as a team, region, or category.
-
C.
IIHFCode
Indicates the standardized code assigned by the International Ice Hockey Federation (IIHF) to identify a national ice hockey association or team.
-
D.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
-
E.
NHLparentClub
Indicates that one hockey team serves as the parent or primary affiliate organization for another team within the NHL system.
- F. None of above. chosen
Provenance (4 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed3e4cc8190ba6aff3bd1adb06f |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd5439c8190aea661b8b4aa51e9 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2ee8b56d08190bd625626353d01b4 |
completed | Feb. 28, 2026, 1:32 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.