Triple
T25209184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobody Owens |
E631634
|
entity |
| Predicate | adoptiveParentsType |
P112915
|
FINISHED |
| Object | ghosts |
—
|
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: ghosts | Statement: [Nobody Owens, adoptiveParentsType, ghosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptiveParentsType Context triple: [Nobody Owens, adoptiveParentsType, ghosts]
-
A.
adoptiveParent
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.
adoptiveStructure
Indicates a structural relationship where one entity has been adopted into, or functions as, the adopted counterpart of another entity within a system or hierarchy.
-
D.
adoptionType
chosen
Indicates the specific category or manner in which an adoption relationship is established or recognized between entities.
-
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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 12:57 p.m.