Triple
T6890676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petr |
E159035
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Petro |
E75297
|
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: Petro | Statement: [Petr, hasVariant, Petro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petro Context triple: [Petr, hasVariant, Petro]
-
A.
Petro
chosen
Petro is a common Ukrainian male given name, notably borne by former Ukrainian president Petro Poroshenko.
-
B.
Petro lwa
Petro lwa are a fiery, aggressive family of spirits in Haitian Vodou associated with power, protection, and revolutionary energy.
-
C.
Petrovich
Petrovich is a Russian patronymic meaning "son of Pyotr (Peter)," commonly used as a middle name in Russian naming conventions.
-
D.
Musina
Musina is a northern South African town in Limpopo Province, known as a key border and transport hub near Zimbabwe and for its history of copper and iron ore mining.
-
E.
Petrichenko
Petrichenko is a Slavic surname, most notably borne by Stepan Petrichenko, a key figure in the Kronstadt rebellion of 1921.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d92d45f08190a730b3842c95b521 |
completed | March 27, 2026, 7:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c748d16e5c81909e35db99af5cfa51 |
completed | March 28, 2026, 3:19 a.m. |
Created at: March 27, 2026, 2:24 p.m.