Triple
T27927156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario Balotelli |
E707868
|
entity |
| Predicate | hasSurnameBeforeAdoption |
P58601
|
FINISHED |
| Object | Barwuah |
—
|
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: Barwuah | Statement: [Mario Balotelli, hasSurnameBeforeAdoption, Barwuah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameBeforeAdoption Context triple: [Mario Balotelli, hasSurnameBeforeAdoption, Barwuah]
-
A.
laterTakesSurnameFrom
Indicates that one entity adopts or assumes the surname of another entity at a later point in time.
-
B.
adoptedFamilyName
chosen
Indicates that an entity has taken or been given a family name different from their original one, typically through adoption, marriage, or personal choice.
-
C.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
D.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
E.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
- F. None of above.
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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 27, 2026, 7 p.m.