Triple
T33915046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sully |
E869427
|
entity |
| Predicate | hasAssociatedSurname |
P49952
|
FINISHED |
| Object | Sullivan |
—
|
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: Sullivan | Statement: [Sully, hasAssociatedSurname, Sullivan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedSurname Context triple: [Sully, hasAssociatedSurname, Sullivan]
-
A.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
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.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
D.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
E.
hasSurnameRegionAssociation
Indicates that there is a relationship between a surname and a geographic region, such as origin, prevalence, or cultural association.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:48 a.m.