Triple
T23398809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dražen Petrović |
E559439
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Petrović |
—
|
NE NERFINISHED |
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: [Dražen Petrović, familyName, Petrović]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petrović Context triple: [Dražen Petrović, familyName, Petrović]
-
A.
Petrović
chosen
Petrović is a common South Slavic surname, notably borne by Croatian basketball legend Dražen Petrović.
-
B.
Radivojevič
Radivojevič is a Slavic surname most notably borne by Slovak former professional ice hockey player Branko Radivojevič.
-
C.
Pavković
Pavković is a South Slavic surname commonly found in Serbia and neighboring countries.
-
D.
Radosavljević
Radosavljević is a Serbian surname, notably borne by former professional footballer and coach Predrag "Preki" Radosavljević.
-
E.
Pupinović
Pupinović is a South Slavic surname variant derived from the name Pupin, typically indicating familial or patronymic origin.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4ddcb9481909881c77458c59c83 |
completed | April 29, 2026, 6:27 a.m. |
Created at: April 17, 2026, 5:37 p.m.