Triple
T3777921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Petrenko |
E83351
|
entity |
| Predicate | active in |
P7685
|
FINISHED |
| Object | 20th-century figure skating |
—
|
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: 20th-century figure skating | Statement: [Viktor Petrenko, active in, 20th-century figure skating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: active in Context triple: [Viktor Petrenko, active in, 20th-century figure skating]
-
A.
isActive
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
B.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
C.
activeInYear
Indicates that an entity was active, functioning, or operational during a specified year.
-
D.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
E.
historicallyActiveIn
chosen
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc5d3dbc8190b6ab118a56acd5a3 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.