Triple
T37842336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banzai Pipeline |
E943510
|
entity |
| Predicate | breaksLeft |
P161020
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Banzai Pipeline, breaksLeft, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksLeft Context triple: [Banzai Pipeline, breaksLeft, true]
-
A.
breaksOver
Indicates that one entity moves or crashes forcefully onto the surface or boundary of another entity, typically dispersing or shattering upon contact.
-
B.
breaksOn
Indicates that one entity fractures, shatters, or fails when subjected to contact with or force from another entity.
-
C.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
D.
breaksBestOn
Indicates that something performs optimally or is most effective when it breaks or is broken under certain conditions or against certain targets.
-
E.
breakDirection
chosen
Indicates the direction in which something breaks, splits, or fractures relative to a reference point or orientation.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.