Triple
T25361774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garbitsch |
E635986
|
entity |
| Predicate | hasLastNameVariant |
P16885
|
FINISHED |
| Object | Garbitsch (pun on "garbage") |
—
|
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: Garbitsch (pun on "garbage") | Statement: [Garbitsch, hasLastNameVariant, Garbitsch (pun on "garbage")]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLastNameVariant Context triple: [Garbitsch, hasLastNameVariant, Garbitsch (pun on "garbage")]
-
A.
nameHasVariant
Indicates that an entity’s name has an alternative or variant form.
-
B.
surnameVariant
chosen
Indicates that one surname is an alternative spelling, form, or variation of another surname.
-
C.
languageOfSurnameVariants
Indicates the language in which particular surname variants are used or originate.
-
D.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
E.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 21, 2026, 1:36 p.m.