Triple
T19452848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzanne Warren |
E486655
|
entity |
| Predicate | hasAdoptiveParents |
P37844
|
FINISHED |
| Object | white adoptive parents |
—
|
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: white adoptive parents | Statement: [Suzanne Warren, hasAdoptiveParents, white adoptive parents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdoptiveParents Context triple: [Suzanne Warren, hasAdoptiveParents, white adoptive parents]
-
A.
adoptiveParent
chosen
Indicates that one entity is the legally recognized parent of another through adoption rather than biological descent.
-
B.
adoptiveFamily
Indicates a familial relationship formed through legal adoption rather than biological descent.
-
C.
hasAdoptiveNationality
Indicates that an entity holds a nationality acquired through adoption rather than by birth or original citizenship.
-
D.
adoptiveChild
Indicates that one entity is the child of another through legal adoption rather than biological descent.
-
E.
adoptedThrough
Indicates that an adoption relationship was established or carried out by means of a specified process, channel, or intermediary.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6339407a08190a3e0213bfbb4df3d |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.