Triple
T3701257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydia Beals Jackson Beecher |
E78582
|
entity |
| Predicate | spouseNotability |
P19181
|
FINISHED |
| Object | prominent American clergyman |
—
|
LITERAL 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: prominent American clergyman | Statement: [Lydia Beals Jackson Beecher, spouseNotability, prominent American clergyman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseNotability Context triple: [Lydia Beals Jackson Beecher, spouseNotability, prominent American clergyman]
-
A.
spouseNotableFor
chosen
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
C.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
D.
spouseNotableWorkField
Indicates that the notable work or professional field associated with a person’s spouse is being specified.
-
E.
spouseAlsoKnownAs
Indicates that a person’s spouse is referred to by an alternative name or alias.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc547c1848190a1ece46c59b7c43d |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.