Triple
T15736621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris Gnedenko |
E381488
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Boris |
E1032081
|
NE 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: Boris | Statement: [Boris Gnedenko, givenName, Boris]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boris Context triple: [Boris Gnedenko, givenName, Boris]
-
A.
Boris
Boris is the given name of Boris Johnson, the former Prime Minister of the United Kingdom and prominent British Conservative politician.
-
B.
Boris
Boris is the given first name of the Argentine-American composer and pianist Lalo Schifrin, known for his film and television scores such as the Mission: Impossible theme.
-
C.
Boris
Boris is the tragic young Soviet soldier and romantic lead in the acclaimed 1957 war drama film "The Cranes Are Flying."
-
D.
Boris
Boris is a Japanese experimental band known for its genre-blending sound that spans drone, metal, noise, and ambient music.
-
E.
Boris
chosen
Boris is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fd6eb888190b7a9b07b76e62c0d |
completed | April 16, 2026, 2:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff8300a4248190ba52573b57f31b36 |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 10, 2026, 4:46 a.m.