Triple
T26394820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDS-1 test |
E663518
|
entity |
| Predicate | programLeader |
P61731
|
FINISHED |
| Object | Igor Kurchatov |
—
|
NE NERFINISHED |
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: Igor Kurchatov | Statement: [RDS-1 test, programLeader, Igor Kurchatov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programLeader Context triple: [RDS-1 test, programLeader, Igor Kurchatov]
-
A.
campaignLeader
Indicates that one entity serves as the primary leader or head responsible for directing and managing a particular campaign involving another entity.
-
B.
designatedLeader
chosen
Indicates that one entity has been formally chosen or assigned to serve as the leader of another entity or group.
-
C.
leaderOfGroup
Indicates that an entity holds a leadership role or primary authority over a particular group.
-
D.
seriesLeader
Indicates that one entity serves as the primary leader, head, or main responsible figure for a particular series involving another entity.
-
E.
principalOrganizer
Indicates that an entity serves as the main or leading organizer responsible for planning or coordinating another entity or event.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 11:28 p.m.