Triple
T35830058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Barry |
E1035771
|
entity |
| Predicate | birthNameSpouseOf |
P45668
|
FINISHED |
| Object | Mary Cleary |
—
|
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: Mary Cleary | Statement: [John Barry, birthNameSpouseOf, Mary Cleary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthNameSpouseOf Context triple: [John Barry, birthNameSpouseOf, Mary Cleary]
-
A.
eraNameOfSpouse
Indicates that the value is the name of the historical era associated with the spouse of the subject.
-
B.
spouseBirthName
chosen
Indicates the birth name of a person's spouse, prior to any name changes such as through marriage.
-
C.
spouseAlsoKnownAs
Indicates that a person’s spouse is referred to by an alternative name or alias.
-
D.
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.
-
E.
spouseNameAtMarriage
Indicates the full name a person’s spouse had at the time of their marriage.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.