Triple
T14651620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | centre (ice hockey) |
E343999
|
entity |
| Predicate | defensiveResponsibility |
P115215
|
FINISHED |
| Object | backchecking |
—
|
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: backchecking | Statement: [centre (ice hockey), defensiveResponsibility, backchecking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveResponsibility Context triple: [centre (ice hockey), defensiveResponsibility, backchecking]
-
A.
defensiveTask
Indicates a task in which an entity protects, guards, or defends another entity or resource from potential threats or harm.
-
B.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
C.
defensiveSkillEmphasized
Indicates that particular focus or priority is placed on developing or utilizing defensive skills in the relevant context.
-
D.
defensivePlan
Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
-
E.
hasDefensiveWork
Indicates that an entity possesses or is associated with a work focused on defense or protective functions.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb517e7648190b9fc73d6cdbb68de |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:27 a.m.