Triple
T9280758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Kosta |
E223059
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kosta |
E584283
|
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: Kosta | Statement: [Michael Kosta, familyName, Kosta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kosta Context triple: [Michael Kosta, familyName, Kosta]
-
A.
Kosta
chosen
Kosta is a diminutive form of the given name Konstantin, commonly used in various Slavic languages.
-
B.
Kostava
Kostava is a Georgian surname most notably borne by Merab Kostava, a prominent Soviet-era Georgian dissident and national independence activist.
-
C.
Koutsovlachs
Koutsovlachs is a Greek-derived exonym historically used—often with a pejorative nuance—for the Aromanian (Vlach) communities of the Balkans.
-
D.
Kostik
Kostik is a common Russian diminutive form of the male given name Konstantin, typically used in informal or affectionate contexts.
-
E.
Micali
Micali is an Italian surname most notably associated with Silvio Micali, a Turing Award–winning computer scientist and cryptographer.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07cd9a1c8190af0521baa428ce10 |
completed | April 1, 2026, 11:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0b1fef1508190a9bf1a55dd39c0ac |
completed | April 4, 2026, 6:38 a.m. |
Created at: March 30, 2026, 7:34 p.m.