Triple
T260008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koba |
E5519
|
entity |
| Predicate | notableUserRole |
P22
|
FINISHED |
| Object | Bolshevik revolutionary leader |
—
|
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: Bolshevik revolutionary leader | Statement: [Koba, notableUserRole, Bolshevik revolutionary leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUserRole Context triple: [Koba, notableUserRole, Bolshevik revolutionary leader]
-
A.
notableParticipant
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
B.
notableUser
Indicates that the user holds a special or distinguished status, such as being recognized, influential, or otherwise noteworthy within a given context.
-
C.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableProponent
Indicates that an entity is a well-known advocate or supporter of another entity, idea, or practice.
-
E.
notablePersonnel
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25f921c2881908821ca2c03815eae |
completed | Feb. 28, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69a25b6b3ea88190bbd858999e42efae |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.