Triple
T17511248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacoby Shaddix |
E426452
|
entity |
| Predicate | hasDiscussedPublicly |
P3281
|
FINISHED |
| Object | mental health issues |
—
|
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 health issues | Statement: [Jacoby Shaddix, hasDiscussedPublicly, mental health issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscussedPublicly Context triple: [Jacoby Shaddix, hasDiscussedPublicly, mental health issues]
-
A.
hasSpokenAbout
chosen
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
B.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
-
C.
hasPublicActivity
Indicates that an entity engages in actions or behaviors that are visible or accessible to the general public.
-
D.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
E.
spokenBefore
Indicates that one entity has spoken or produced speech earlier in time than another 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4525c21c88190a9394c4bce006a38 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.