Triple
T3153018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harilal Gandhi |
E65919
|
entity |
| Predicate | struggledWith |
P36801
|
FINISHED |
| Object | alcoholism |
—
|
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: alcoholism | Statement: [Harilal Gandhi, struggledWith, alcoholism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: struggledWith Context triple: [Harilal Gandhi, struggledWith, alcoholism]
-
A.
associatedWithStruggle
Indicates a relationship in which an entity is connected to, involved in, or characterized by a particular struggle, conflict, or hardship.
-
B.
notableStruggles
chosen
Indicates that the subject has faced significant challenges, difficulties, or adversities that are especially noteworthy or defining.
-
C.
struggleFor
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
-
D.
challengeUndertaken
Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
-
E.
triedToAvoid
Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5c3d6d481908c296e9e09c07f6f |
completed | March 8, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.