Triple
T34804606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daddy Johnson |
E1003318
|
entity |
| Predicate | adoptiveParentStatus |
P164499
|
FINISHED |
| Object | adoptive father |
—
|
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: adoptive father | Statement: [Daddy Johnson, adoptiveParentStatus, adoptive father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptiveParentStatus Context triple: [Daddy Johnson, adoptiveParentStatus, adoptive father]
-
A.
adoptionStatus
Indicates the current state or outcome of an adoption relationship or process between entities.
-
B.
adoptiveParent
Indicates that one entity is the legally recognized parent of another through adoption rather than biological descent.
-
C.
parentalRelationshipStatusAtAdoption
Indicates the type and condition of the parent–child relationship that existed at the time the adoption took place.
-
D.
adoptiveRelationshipType
chosen
Indicates the specific nature of an adoptive relationship that exists between two entities (e.g., adoptive parent, adopted child).
-
E.
adoptiveChild
Indicates that one entity is the child of another through legal adoption rather than biological descent.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77a8cf978819086a26dbbbd31d9a2 |
completed | May 3, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.