Triple
T16007726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Bishop |
E388259
|
entity |
| Predicate | causeOfInstitutionalization |
P120746
|
FINISHED |
| Object | mental breakdown |
—
|
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: mental breakdown | Statement: [Walter Bishop, causeOfInstitutionalization, mental breakdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfInstitutionalization Context triple: [Walter Bishop, causeOfInstitutionalization, mental breakdown]
-
A.
causeOfMarginalization
Indicates a factor, action, or condition that contributes to the social, economic, or political marginalization of an entity.
-
B.
causeOfDisability
Indicates that one entity is the reason or source that brings about another entity’s disability.
-
C.
reasonForDemise
Indicates the cause, circumstance, or factor that led to an entity’s death or termination.
-
D.
reasonForStay
Indicates the underlying cause, purpose, or circumstance that explains why an entity remains or is staying in a particular place or situation.
-
E.
purposeOfPlacement
Indicates that something has been placed or positioned with the specific aim, function, or intended use of that placement.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:55 a.m.