Triple
T11923153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zora Petrović |
E283708
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Petrović |
E559439
|
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: Petrović | Statement: [Zora Petrović, familyName, Petrović]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petrović Context triple: [Zora Petrović, familyName, Petrović]
-
A.
Petrović
chosen
Petrović is a common South Slavic surname, notably borne by Croatian basketball legend Dražen Petrović.
-
B.
Radosavljević
Radosavljević is a Serbian surname, notably borne by former professional footballer and coach Predrag "Preki" Radosavljević.
-
C.
Pupinović
Pupinović is a South Slavic surname variant derived from the name Pupin, typically indicating familial or patronymic origin.
-
D.
Vujović
Vujović is a South Slavic surname of Montenegrin and Serbian origin, borne by various notable figures in the Balkans and beyond.
-
E.
Rajaković
Rajaković is a Serbian surname most notably associated with NBA coach Darko Rajaković.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e2fc648190a446c1917db1c7d9 |
completed | April 10, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f45891f9c081909250a0aa0f7448d2 |
completed | May 1, 2026, 7:38 a.m. |
Created at: April 8, 2026, 9:45 p.m.