Triple
T20959906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurence Eusden |
E516209
|
entity |
| Predicate | allegedProblem |
P45135
|
FINISHED |
| Object | alcohol abuse |
—
|
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: alcohol abuse | Statement: [Laurence Eusden, allegedProblem, alcohol abuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedProblem Context triple: [Laurence Eusden, allegedProblem, alcohol abuse]
-
A.
complainsAbout
Indicates that one entity expresses dissatisfaction, criticism, or grievances regarding another entity or situation.
-
B.
possibleIssue
chosen
Indicates that there is a potential or suspected problem, defect, or undesired condition associated with the referenced entity or situation, though it is not yet confirmed.
-
C.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
-
D.
concernsProblem
Indicates that something is about, related to, or deals with a particular problem or issue.
-
E.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6e50988190a564d2aaf1a9bc54 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:30 p.m.