Triple
T30058281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleg Blokhin |
E763794
|
entity |
| Predicate | appearancesForDynamoKyiv |
P184381
|
FINISHED |
| Object | over 400 official matches |
—
|
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: over 400 official matches | Statement: [Oleg Blokhin, appearancesForDynamoKyiv, over 400 official matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearancesForDynamoKyiv Context triple: [Oleg Blokhin, appearancesForDynamoKyiv, over 400 official matches]
-
A.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
B.
appearedWith
Indicates that two entities were present or participated together in the same context, event, or medium.
-
C.
testAppearances
Indicates that one entity conducts or is involved in tests or experiments concerning the appearances or visual characteristics of another entity.
-
D.
appearedAt
Indicates that an entity was present or made an appearance at a specific event, location, or occasion.
-
E.
homeVenueAppearances
Indicates the number of times an entity has appeared or performed at its designated home venue.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 29, 2026, 6:57 p.m.