Triple
T29757298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wendy Treece Bridges |
E753062
|
entity |
| Predicate | spouseSiblingInLaw |
P179791
|
FINISHED |
| Object | Jeff Bridges |
—
|
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: Jeff Bridges | Statement: [Wendy Treece Bridges, spouseSiblingInLaw, Jeff Bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseSiblingInLaw Context triple: [Wendy Treece Bridges, spouseSiblingInLaw, Jeff Bridges]
-
A.
spouseRelative
chosen
Indicates that one person is related to another through the marriage of at least one of them (e.g., in-laws or relatives by marriage).
-
B.
spouseOfSiblingOf
Indicates the person who is married to someone’s sibling.
-
C.
brotherInLaw
Indicates a relationship where one person is the brother of someone's spouse, the spouse of someone's sibling, or the spouse of the sibling of someone's spouse.
-
D.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
-
E.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 7:57 p.m.