Triple
T31916759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pison |
E814852
|
entity |
| Predicate | relatedCognomen |
P49952
|
FINISHED |
| Object | Piso |
E1036977
|
NE FINISHED |
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: Piso | Statement: [Pison, relatedCognomen, Piso]
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 (4 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb136e510819098db7d0e36be0915 |
completed | June 14, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:02 a.m.