Triple
T37017597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Germany men's national ice hockey team |
E916125
|
entity |
| Predicate | representedPeriodStart |
P200553
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [West Germany men's national ice hockey team, representedPeriodStart, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedPeriodStart Context triple: [West Germany men's national ice hockey team, representedPeriodStart, 1949]
-
A.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
-
B.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
-
C.
narratedPeriodStart
Indicates the point in time at which the narrated or described period begins.
-
D.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
E.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
| PDg | Predicate description generation | batch_69ff956cd640819081efc31f313690b0 |
completed | May 9, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:14 p.m.