Triple
T33260507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amanda Brundage |
E851494
|
entity |
| Predicate | usesSurnameAfterMarriage |
P14292
|
FINISHED |
| Object | Brundage |
—
|
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: Brundage | Statement: [Amanda Brundage, usesSurnameAfterMarriage, Brundage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSurnameAfterMarriage Context triple: [Amanda Brundage, usesSurnameAfterMarriage, Brundage]
-
A.
hasMarriedSurname
chosen
Indicates that a person’s current surname is the one they adopted through marriage.
-
B.
hasFamilyNameAfterSecondMarriage
Indicates that an entity’s family name is the one adopted following their second marriage.
-
C.
usedSurnameFor
Indicates that one entity adopted or employed another entity’s surname as the name by which they were known or referred to.
-
D.
maidenNameOf
Indicates that one person’s original family surname before marriage is the maiden name of another person.
-
E.
laterMarriedName
Indicates that the referenced name is a surname or full name a person adopted after a later marriage, replacing or succeeding their previous name.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 1:31 a.m.