Triple
T34371633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buchinsky |
E882170
|
entity |
| Predicate | alternativeSurnameOf |
P16885
|
FINISHED |
| Object | Charles Bronson |
—
|
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: Charles Bronson | Statement: [Buchinsky, alternativeSurnameOf, Charles Bronson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeSurnameOf Context triple: [Buchinsky, alternativeSurnameOf, Charles Bronson]
-
A.
surnameVariant
chosen
Indicates that one surname is an alternative spelling, form, or variation of another surname.
-
B.
equivalentSurname
Indicates that two entities share the same surname or are considered to have matching surnames for identification or equivalence purposes.
-
C.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
D.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
E.
equivalentSurnameInGerman
Indicates that two surnames are equivalent to each other when translated into or represented in the German language.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1:59 a.m.