Triple
T6692393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIHF Congress |
E152657
|
entity |
| Predicate | canWithdraw |
P72242
|
FINISHED |
| Object | IIHF membership |
—
|
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: IIHF membership | Statement: [IIHF Congress, canWithdraw, IIHF membership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canWithdraw Context triple: [IIHF Congress, canWithdraw, IIHF membership]
-
A.
canWithdrawConfidenceFrom
Indicates that an entity has the authority or ability to revoke or remove its previously given confidence or support from another entity.
-
B.
withdrawalType
Indicates the specific method or category by which a withdrawal is carried out in a given context.
-
C.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense of another entity.
-
D.
canBorrowFrom
Indicates that one entity is permitted or able to borrow something (such as resources, items, or privileges) from another entity.
-
E.
withdrewFrom
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cd0d939081908ede0bb6ce19f559 |
completed | March 27, 2026, 6:31 p.m. |
Created at: March 27, 2026, 2:05 p.m.