Triple
T10102069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain "Howling Mad" Murdock |
E216225
|
entity |
| Predicate | hasMentalHealthStatus |
P4720
|
FINISHED |
| Object | often considered insane |
—
|
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: often considered insane | Statement: [Captain "Howling Mad" Murdock, hasMentalHealthStatus, often considered insane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMentalHealthStatus Context triple: [Captain "Howling Mad" Murdock, hasMentalHealthStatus, often considered insane]
-
A.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
B.
hasMood
Indicates that an entity is experiencing or characterized by a particular emotional or affective state.
-
C.
hasHealthConcern
chosen
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
D.
hasPossibleSymptom
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
-
E.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd099c21c819097aac4f0f168a2da |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.