Triple
T35748298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goolagong-Cawley |
E1033245
|
entity |
| Predicate | hasMaidenNamePart |
P36176
|
FINISHED |
| Object | Goolagong |
E2160716
|
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: Goolagong | Statement: [Goolagong-Cawley, hasMaidenNamePart, Goolagong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaidenNamePart Context triple: [Goolagong-Cawley, hasMaidenNamePart, Goolagong]
-
A.
maidenNameOf
chosen
Indicates that one person’s original family surname before marriage is the maiden name of another person.
-
B.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
-
C.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
-
D.
hasInitialOnlySurname
Indicates that a person is represented by only the initial of their given name together with their full surname, rather than their complete given name.
-
E.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a02f441bd408190923b6b68adee8fde |
completed | May 12, 2026, 9:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38bfc0bc5081908e8608d58fd66b60 |
completed | June 22, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_6a02f3c1e64881908569423c9f298f26 |
completed | May 12, 2026, 9:32 a.m. |
Created at: May 3, 2026, 4:06 p.m.