Triple
T21874174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Day69 |
E540086
|
entity |
| Predicate | helpedPropel |
P33868
|
FINISHED |
| Object | 6ix9ine to mainstream attention |
—
|
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: 6ix9ine to mainstream attention | Statement: [Day69, helpedPropel, 6ix9ine to mainstream attention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedPropel Context triple: [Day69, helpedPropel, 6ix9ine to mainstream attention]
-
A.
helpedLaunch
Indicates that one entity played a significant role in initiating, starting, or bringing another entity (such as a project, product, or organization) into operation or public release.
-
B.
helpedCause
chosen
Indicates that one entity contributed to bringing about, enabling, or facilitating an outcome or event involving another entity.
-
C.
helpsIn
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
-
D.
laterHelps
Indicates that one entity provides help or assistance to another at a subsequent time rather than immediately.
-
E.
helpedDiscover
Indicates that one entity assisted another entity in the process of discovering or uncovering something.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f338757c81908005bfedb52b03cc |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:01 p.m.