Triple
T2509104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olga Korbut |
E52657
|
entity |
| Predicate | eventSpecialization |
P37115
|
FINISHED |
| Object | balance beam |
—
|
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: balance beam | Statement: [Olga Korbut, eventSpecialization, balance beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventSpecialization Context triple: [Olga Korbut, eventSpecialization, balance beam]
-
A.
eventSpecialty
chosen
Indicates the specific field, theme, or area of focus that an event is primarily concerned with.
-
B.
specialtyEvent
Indicates that an event is designated as a special or distinctive occurrence, often differing from regular or routine events in nature or purpose.
-
C.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
D.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
E.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd65d6a988190aaaac8e98540a14f |
completed | March 7, 2026, 7:40 a.m. |
| PD | Predicate disambiguation | batch_69abd0bd996c8190ba8b9d6e4333b8d4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.