Triple
T22805284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Men's Handball Championship |
E564514
|
entity |
| Predicate | typicalHeldEvery |
P109651
|
FINISHED |
| Object | 2 years |
—
|
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: 2 years | Statement: [World Men's Handball Championship, typicalHeldEvery, 2 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHeldEvery Context triple: [World Men's Handball Championship, typicalHeldEvery, 2 years]
-
A.
isHeldEvery
chosen
Indicates that an event or activity occurs regularly on every specified time interval or occasion.
-
B.
typicallyHolds
Indicates that a certain relationship or condition generally holds true in typical or normal situations, though not necessarily in all cases.
-
C.
heldEvery
Indicates that an entity consistently possessed or maintained control of another entity throughout every instance or period within a specified range.
-
D.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
E.
automaticallyHeld
Indicates that the holding or possession relationship occurs by default or system rule, without requiring an explicit action or decision by the involved entities.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5b37cc8190a41d8f304ba8d609 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.