Triple
T14121408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobra Bubbles |
E339912
|
entity |
| Predicate | ultimately |
P112893
|
FINISHED |
| Object | supports keeping Lilo and Nani together |
—
|
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: supports keeping Lilo and Nani together | Statement: [Cobra Bubbles, ultimately, supports keeping Lilo and Nani together]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimately Context triple: [Cobra Bubbles, ultimately, supports keeping Lilo and Nani together]
-
A.
ultimatelyDoesNot
Indicates that, despite any preceding conditions or possibilities, the referenced entity or action does not in the end occur, hold, or get carried out.
-
B.
ultimateState
Indicates the final or end condition that an entity or process ultimately reaches after all preceding stages or transitions.
-
C.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
D.
uso
Indicates that one entity uses, employs, or makes use of another entity for some purpose or function.
-
E.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
- F. None of above. chosen
Provenance (4 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de60942a588190beff0058a92f7051 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.