Triple
T26515974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadine Breyer |
E669813
|
entity |
| Predicate | hasImmediateFamilyMember |
P7844
|
FINISHED |
| Object | Stephen G. Breyer |
—
|
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: Stephen G. Breyer | Statement: [Nadine Breyer, hasImmediateFamilyMember, Stephen G. Breyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmediateFamilyMember Context triple: [Nadine Breyer, hasImmediateFamilyMember, Stephen G. Breyer]
-
A.
hasNotableFamilyMembers
Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
-
B.
hasHouseholdMember
Indicates that one entity is a member of the same household as another entity.
-
C.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
D.
hasOnScreenFamilyMember
Indicates that one entity appears on screen as a family member of another entity.
-
E.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 1:23 a.m.