Triple
T28700468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL defensemen |
E729536
|
entity |
| Predicate | positionOnIce |
P3250
|
FINISHED |
| Object | blue line in offensive zone |
—
|
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: blue line in offensive zone | Statement: [NHL defensemen, positionOnIce, blue line in offensive zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnIce Context triple: [NHL defensemen, positionOnIce, blue line in offensive zone]
-
A.
performedOnIceRink
Indicates that an action or event took place on an ice rink as its physical setting or surface.
-
B.
iceSurface
Indicates that something is located on, in contact with, or forming the surface of ice.
-
C.
playsOnRinkType
Indicates that an entity participates in a game or activity on a specific type of rink surface or rink configuration.
-
D.
positionOn
chosen
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
usesStandardIceRink
Indicates that the activity, event, or entity operates on or is conducted within a regulation-size, standard ice rink.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 28, 2026, 5:42 a.m.