Triple
T2664877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Corbett |
E55610
|
entity |
| Predicate | mentalHealth |
P33305
|
FINISHED |
| Object | reported mental instability |
—
|
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: reported mental instability | Statement: [Boston Corbett, mentalHealth, reported mental instability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentalHealth Context triple: [Boston Corbett, mentalHealth, reported mental instability]
-
A.
care
Indicates showing concern, attention, or responsibility for the well-being or needs of another entity.
-
B.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
C.
topicOfAdvice
Indicates that one entity is the subject or focus about which advice is being given by another entity.
-
D.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
E.
healthIndicator
chosen
Indicates a measure or signal that reflects the health status or condition of an entity.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd96dba44819085c3e651afba7806 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.