Triple
T29413195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Leszczyński |
E745950
|
entity |
| Predicate | hasPluralSurnameForm |
P180221
|
FINISHED |
| Object | Leszczyńscy |
—
|
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: Leszczyńscy | Statement: [House of Leszczyński, hasPluralSurnameForm, Leszczyńscy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPluralSurnameForm Context triple: [House of Leszczyński, hasPluralSurnameForm, Leszczyńscy]
-
A.
hasPluralFamilyNameForm
chosen
Indicates that an entity’s family name has a corresponding pluralized form used to refer to multiple members of the family.
-
B.
hasPluralForm
Indicates that one term is the plural grammatical form of another term.
-
C.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
D.
isCompoundSurname
Indicates that a surname consists of two or more distinct name elements combined into a single family name.
-
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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 28, 2026, 2:58 p.m.