Triple
T26436576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Things First Foundation |
E664964
|
entity |
| Predicate | notableFounderSpouse |
P113119
|
FINISHED |
| Object | Brenda Warner |
—
|
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: Brenda Warner | Statement: [First Things First Foundation, notableFounderSpouse, Brenda Warner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFounderSpouse Context triple: [First Things First Foundation, notableFounderSpouse, Brenda Warner]
-
A.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
spouse notableWork
Indicates that a person's spouse is significantly associated with a particular notable work.
-
C.
spouseOfFounderOf
Indicates that one entity is the spouse of another entity who is the founder of a specified organization or entity.
-
D.
spouseOfFounder
chosen
Indicates that one entity is the spouse (married partner) of the founder of another entity.
-
E.
spouseFatherInLawNotableFor
Indicates that a person’s spouse’s father (their father-in-law) is notable or distinguished for a particular achievement, role, or characteristic.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: April 26, 2026, 11:54 p.m.