Triple
T7905748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whip Whitaker |
E183570
|
entity |
| Predicate | confessesTo |
P40219
|
FINISHED |
| Object | being drunk on the day of the crash |
—
|
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: being drunk on the day of the crash | Statement: [Whip Whitaker, confessesTo, being drunk on the day of the crash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confessesTo Context triple: [Whip Whitaker, confessesTo, being drunk on the day of the crash]
-
A.
confessedTo
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another entity.
-
B.
confesses
chosen
Indicates that one entity openly admits or acknowledges something, typically a wrongdoing, secret, or previously concealed fact, to another entity.
-
C.
confessedAs
Indicates that one entity has admitted or acknowledged being or doing something, typically revealing guilt, identity, or involvement in relation to another entity.
-
D.
confessedFor
Indicates that one entity admitted guilt or responsibility on behalf of another entity.
-
E.
confessedBy
Indicates that a particular admission or acknowledgment of guilt, wrongdoing, or truth was made by a specific 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a56c9f0819094dc87fe55a8823e |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.