Triple
T31916759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pison |
E814852
|
entity |
| Predicate | relatedCognomen |
—
|
GENERATED |
| Object | Piso |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCognomen Context triple: [Pison, relatedCognomen, Piso]
-
A.
etymologyOfCognomen
Indicates that one term specifies the linguistic origin or derivation of a particular cognomen (surname or family name).
-
B.
associatedSurname
chosen
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
C.
cognomenOf
Indicates that one entity is the cognomen (surname or family name) of another entity.
-
D.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
-
E.
nameCognateOf
Indicates that two names share a common linguistic origin or form, typically due to derivation from the same root or historical source.
- F. None of above.
Provenance (1 batch)
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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:02 a.m.