Triple
T21540327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Hockey League |
E531465
|
entity |
| Predicate | allowsBodyChecking |
P144157
|
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: [Ontario Hockey League, allowsBodyChecking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsBodyChecking Context triple: [Ontario Hockey League, allowsBodyChecking, yes]
-
A.
supportsBody
Indicates that one entity physically or structurally holds up, bears the weight of, or provides foundational stability for another entity’s body.
-
B.
usesBody
Indicates that one entity employs or utilizes the physical body of another (or its own) as a means or instrument to perform an action or function.
-
C.
requiresBody
Indicates that one entity cannot exist, function, or be valid without being associated with or contained within another entity that serves as its body.
-
D.
supportsBodyType
Indicates that one entity is compatible with, designed for, or can accommodate a specified body type.
-
E.
haveBody
Indicates that one entity possesses, contains, or is associated with another entity as its body or main physical/content component.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d119e0c8190a207c0e8ae328a95 |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:28 p.m.