Triple
T29804543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cody Morgan |
E756803
|
entity |
| Predicate | previouslyInCareOf |
P194750
|
FINISHED |
| Object | foster care system |
—
|
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: foster care system | Statement: [Cody Morgan, previouslyInCareOf, foster care system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyInCareOf Context triple: [Cody Morgan, previouslyInCareOf, foster care system]
-
A.
isUnderCareOf
Indicates that one entity is receiving care, supervision, or management from another entity.
-
B.
previouslyIn
Indicates that an entity was located in, part of, or associated with another entity at some earlier time, but is not necessarily so now.
-
C.
formerPatient
Indicates that one entity was previously a patient of another entity but is no longer under their care.
-
D.
previouslyAdmitted
Indicates that an entity has already been admitted or accepted at an earlier time prior to the current reference point.
-
E.
previouslyLocatedIn
Indicates that an entity was located in a particular place or region at some time in the past, but is not necessarily located there now.
- F. None of above. chosen
Provenance (4 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: April 29, 2026, 5:20 p.m.