Triple
T16497114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Igor Troubetzkoy |
E400712
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Igor |
E401633
|
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: Igor | Statement: [Prince Igor Troubetzkoy, givenName, Igor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Igor Context triple: [Prince Igor Troubetzkoy, givenName, Igor]
-
A.
Igor
Igor is Tyler, the Creator’s critically acclaimed 2019 studio album that blends hip hop, R&B, and neo-soul into a concept-driven exploration of love and heartbreak.
-
B.
Igor
chosen
Igor is a masculine given name of Russian origin, widely used in Slavic countries and beyond.
-
C.
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.
-
D.
Boris
Boris is a Japanese experimental band known for its genre-blending sound that spans drone, metal, noise, and ambient music.
-
E.
Boris
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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e343a7c81909e04cbaaa40e2531 |
completed | April 18, 2026, 7:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00582a316c81908ec32679c976ba23 |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:14 a.m.