Triple
T16521444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Cousins |
E401326
|
entity |
| Predicate | offFieldIssues |
P21734
|
FINISHED |
| Object | substance abuse problems |
—
|
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: substance abuse problems | Statement: [Ben Cousins, offFieldIssues, substance abuse problems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offFieldIssues Context triple: [Ben Cousins, offFieldIssues, substance abuse problems]
-
A.
raisesIssue
Indicates that one entity brings up, reports, or formally submits a concern, problem, or topic for attention to another entity or system.
-
B.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
C.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
D.
numberOfIssues
Indicates the quantity of issues associated with a given entity or context.
-
E.
knownIssue
chosen
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e804e388190b684bde2c82ab770 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.