Triple
T20900086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gumball Watterson |
E514646
|
entity |
| Predicate | oftenGetsInto |
P23735
|
FINISHED |
| Object | trouble |
—
|
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: trouble | Statement: [Gumball Watterson, oftenGetsInto, trouble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenGetsInto Context triple: [Gumball Watterson, oftenGetsInto, trouble]
-
A.
oftenInvolvedWith
chosen
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
-
B.
oftenHave
Indicates that one entity frequently possesses, experiences, or is associated with another entity.
-
C.
runsInto
Indicates that one entity moves so as to collide or come into sudden contact with another entity.
-
D.
oftenTriesToCatch
Indicates that one entity frequently attempts to catch, capture, or seize another entity.
-
E.
typicallyFallsIn
Indicates that one event, period, or occurrence usually happens within the temporal range or bounds of another.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8fa5228819084341dbc813cc1e3 |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.